[ https://issues.apache.org/jira/browse/QPIDJMS-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16576794#comment-16576794 ]
Robbie Gemmell edited comment on QPIDJMS-407 at 8/10/18 8:14 PM: ----------------------------------------------------------------- I'll be looking to release 0.36.0 sometime next week, once proton-j 0.29.0 is available. was (Author: gemmellr): I'll be looking to releae 0.36.0 sometime next week, once proton-j 0.29.0 is available. > Reconnect not working reliable for connections with more than 1 producer JMS > session > ------------------------------------------------------------------------------------ > > Key: QPIDJMS-407 > URL: https://issues.apache.org/jira/browse/QPIDJMS-407 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client > Affects Versions: 0.35.0 > Reporter: Johan Stenberg > Assignee: Timothy Bish > Priority: Critical > Fix For: 0.36.0 > > Attachments: QPIDJMS-407.zip > > > When a JMS connection with more than one producer session looses the > underlying TCP connection to the broker auto reconnect (failover) is not > working properly. After the reconnect attempt no new messages will be sent. > When only one producer session is used, reconnect apparently works as > expected. > I attached a maven project with a test case where the TCP connection is > dropped by the broker to provoke the reconnect attempt. In most cases when I > run the test class the *testAutoReconnectWith2ProducerSessions()* stops > sending messages after the first reconnect attempt. Maybe there occurs some > qpid internal race condition. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org