问题
I am trying to verify the Reconnection strategy in Mule ESB as mentioned in the documentation.
I have set the standard Reconnection strategy with retry attemts as 5 and with some timeout.
(My end point is not reachable, as intentionally stopped it to test the scenario).
I have the exception in the Mule console as: Exception stack is: 1. Connection refused: connect (java.net.ConnectException) java.net.DualStackPlainSocketImpl:-2 (null) 2. Failed to route event via endpoint: DefaultOutboundEndpoint
And then I changed the reconnection strategy to 'connect forever' and tried it. In this case also I got the same error.
My qstn is, if I set the 'Connect forever' feature, then I expect the application to try for re connect untill it gets succeeded. but this is not happenning.
And also in the first scenario, if my retry attemps are 5, then I dont see any loogs mentioning the number of retry attempts made.
Can any one plese explain it in better way whether this reconnection property is actually working in Mule ESB 3.4.
Thanks in advance.
回答1:
HTTP is a disconnected protocol: the reconnection strategies only work for connected protocols, like JMS or JDBC.
I see the error is in an outbound endpoint so I have the impression you are expecting Mule to retry the dispatch, not reconnected the transport.
One way to do retries is to use the until-successful message processor.
来源：https://stackoverflow.com/questions/18727202/reconnection-strategy-in-mule-esb