Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
proton-0.10
-
None
-
None
Description
We are using Mule ESB to integrate with several Qpid message servers. On occasion, an IllegalStateException is thrown while reconnecting resulting in an endless loop of reconnection attempts. The full exception message indicates that the max frame size cannot be set after transport has been initialised. Unfortunately, throwing an exception in this circumstance simply results in an endless loop.
It is understandable that the max frame size should not be set again after the transport has been initialized, but would it be reasonable to log it as a warning and not throw an exception?
Here is an example of the exception we see:
ERROR 2016-09-01 08:21:41,145 [[emxrouter-core].Mule.02] org.mule.retry.notifiers.ConnectNotifier: Failed to connect/reconnect: jms://emx-router. Root Exception was: Cannot set max frame size after transport has been initialised. Type: class java.lang.IllegalStateException