[
https://issues.apache.org/jira/browse/QPIDJMS-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16573260#comment-16573260
]
ASF subversion and git services commented on QPIDJMS-407:
---------------------------------------------------------
Commit fe90adaf2f63444c09ddb6b058f03568cacb04ef in qpid-jms's branch
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=fe90ada ]
QPIDJMS-407 Address thread unsafe failover requests handling
Address thread unsafe handling of in progress requests being added and
removed from the request tracking map that lead to issues on reconnect
and recover losing track of pending requests.
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
