Question:Using mule 4.4 runtime community edition on premise
Am trying to understand
HTTP Listenerbetter and came across this attribute:
When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment will fail if the test doesn’t pass after exhausting the associated reconnection strategy
Now if this was a Database or Messaging broker connector I can relate to ‘reconnection’ , but in case of HTTP Listener what is it really connecting to ?
Does ‘connection’ here really mean the ability for the api to listen / serve incoming requests at specified port ( I am assuming that is what it means )
So if for some reason while the api was being deployed it could not come up then we can use this ‘retry’ mechanism ?
Answer:Sources in connectors -the HTTP Listener in this case- that use connections need to obtain their connection objects. The HTTP Listener is not trying to connect to an external server but needs to setup the HTTP server connection. If there is an error the source may attempt to reestablish the connection. It doesn’t mean that it will reach out, just that the ‘connection’ object is correctly setup and error handling is taking place as the documentation links explain.
If you have better answer, please add a comment about this, thank you!