You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2010/01/19 21:22:54 UTC
[jira] Created: (QPID-2345) Java Client not detecting cause of
session close from client thread
Java Client not detecting cause of session close from client thread
-------------------------------------------------------------------
Key: QPID-2345
URL: https://issues.apache.org/jira/browse/QPID-2345
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.6
Reporter: Martin Ritchie
As exemplified by the SimpleACLTest when the broker closes the connection the client attempts to stop the current activity and remember the cause of the closure to report to the client. However, if the client is in the process of performing a operation such as session.createQueue() the closed state can be deteted before the cause has been set as a result the IllegalStateException is thrown and no cause has been set.
This was working on 0.5. However, it is possible that the new IO layer is highlighting another race condition. Or that it is not correctly setting the state to CLOSED. Which is required to be done to prompt the client threads to check for a causal exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org