Bug 1254588 - AMQP 1.0 jms client hangs when another reconnect should happen on the same MRGM broker
Summary: AMQP 1.0 jms client hangs when another reconnect should happen on the same MR...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-java
Version: 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 3.2
: ---
Assignee: Robbie Gemmell
QA Contact: Michal Toth
URL:
Whiteboard:
Depends On:
Blocks: 1215806
TreeView+ depends on / blocked
 
Reported: 2015-08-18 13:18 UTC by Michal Toth
Modified: 2016-10-10 16:24 UTC (History)
4 users (show)

Fixed In Version: qpid-jms-0.5.0-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-08 13:11:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ENTMQCL-12 0 Major Closed AMQP 1.0 jms client hangs when another reconnect should happen on the same MRGM broker 2019-01-19 15:23:16 UTC
Red Hat Product Errata RHEA-2015:1879 0 normal SHIPPED_LIVE Red Hat Enterprise MRG Messaging 3.2 Release 2015-10-08 17:07:53 UTC

Description Michal Toth 2015-08-18 13:18:40 UTC 
Note: Using qpid-java as component (but referring to the latest pacakged qpid-jms-client 0.3.0)
Comment 1 Michal Toth 2015-08-18 13:23:31 UTC 
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.
Comment 2 JBoss JIRA Server 2015-08-24 14:48:52 UTC 
Robbie Gemmell <rgemmell> updated the status of jira ENTMQCL-12 to Coding In Progress
Comment 3 Robbie Gemmell 2015-08-25 15:03:15 UTC 
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.
Comment 4 Michal Toth 2015-09-01 11:25:55 UTC 
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
Comment 5 JBoss JIRA Server 2015-09-02 09:12:55 UTC 
Robbie Gemmell <rgemmell> updated the status of jira ENTMQCL-12 to Resolved
Comment 7 errata-xmlrpc 2015-10-08 13:11:06 UTC 
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
Comment 8 JBoss JIRA Server 2016-08-12 10:25:40 UTC 
Michal Toth <mtoth> updated the status of jira ENTMQCL-12 to Closed
Comment 9 JBoss JIRA Server 2016-10-10 16:24:13 UTC 
Justin Ross <jross> updated the status of jira ENTMQCL-12 to Reopened
Comment 10 JBoss JIRA Server 2016-10-10 16:24:48 UTC 
Justin Ross <jross> updated the status of jira ENTMQCL-12 to Closed
Note You need to log in before you can comment on or make changes to this bug.