[
https://issues.apache.org/jira/browse/PROTON-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15473872#comment-15473872
]
Mark Soderquist commented on PROTON-1296:
-----------------------------------------
I don't disagree with this assessment. I'll try and get the vendor to update
the usage pattern, but I'm not very hopeful.
> IllegalStateException on reconnect
> ----------------------------------
>
> Key: PROTON-1296
> URL: https://issues.apache.org/jira/browse/PROTON-1296
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Affects Versions: 0.10
> Reporter: Mark Soderquist
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
