Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.2
-
Component/s: Core: (other)
-
Labels:None
-
Similar Issues:None
Description
Connection strategies only work on inbound endpoints. However, it would be nice if we could use the same mechanism for both inbound and outbound endpoints.
For instance if I have this configuration:
<connector name="axis" className="org.mule.providers.soap.axis.AxisConnector">
<connection-strategy className="org.mule.providers.SimpleRetryConnectionStrategy">
<properties>
<property name="retryCount" value="3"/>
<property name="frequency" value="2000"/>
</properties>
</connection-strategy>
</connector>
The AxisConnector could retry a couple of times with a request if (for instance) the destination server is down. It would be even nicer if the error codes or types for the reconnection strategy could be specified. With this I mean that the connector wouldn't retry if it gets a business exception as a response but it will do if an HTTP 404 code is received.
This feature would be really nice.
Right now, Mule plays nice if the inbound endpoint becomes unavailable. It waits and retries nicely according to the chosen strategy.
However, for outbound endpoints, Mule fails the transaction immediately on error. I'm using Mule as a bridge between two JMS providers. This means that if my outbound endpoint goes offline, Mule rapidly throws away a bunch of messages.