Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
2.12.0
-
None
-
Unknown
Description
We've had a case where the component to which the Mina2Producer is communicating changes IP address. This change isn't picked up by our camel route, which uses Mina2. Therefore the communication fails. If the address was looked up each time openConnection is called (for protocols other than VM) this would overcome this problem.
This 'non-caching' of the IP address is configurable. Default is not to have it (ie current behavour). Configuration can be updated with a cachedAddress flag to turn this feature on.
I've made changes to a fork of https://github.com/apache/camel so I'll issue a pull request.