Note: Using qpid-java as component (but referring to the latest pacakged qpid-jms-client 0.3.0)
Qpid-jms-client hangs in a second and subsequent failover reconnect attempt on the same MRG-M broker, with "Transport connection remotely closed". No error is reported and client keeps running.
Robbie Gemmell <rgemmell> updated the status of jira ENTMQCL-12 to Coding In Progress
Changes made upstream look to resolve this. See JIRA ENTMQCL-12 for more comments. Moving to POST until decided on a backport or rebase etc.
Manually verified using qpid-jms-client-0.5.0-1.el6/7 against MRG-M broker. Apart from incorrect number of received messages in destination by broker, the reconnect feature is working correctly. Marking original issue as verified. For incorrect number of messages, see Bug 1087828
Robbie Gemmell <rgemmell> updated the status of jira ENTMQCL-12 to Resolved
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2015-1879.html
Michal Toth <mtoth> updated the status of jira ENTMQCL-12 to Closed
Justin Ross <jross> updated the status of jira ENTMQCL-12 to Reopened
Justin Ross <jross> updated the status of jira ENTMQCL-12 to Closed