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 2009/03/27 18:54:50 UTC
[jira] Updated: (QPID-1779) Session close as a result of
disconnection will block the client
[ https://issues.apache.org/jira/browse/QPID-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-1779:
---------------------------------
Attachment: CloseAfterConnectionFailureTest.java
QPID-1779-SessionCloseBlockFix.patch
> Session close as a result of disconnection will block the client
> ----------------------------------------------------------------
>
> Key: QPID-1779
> URL: https://issues.apache.org/jira/browse/QPID-1779
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: M2.1, M3, M4, 0.5
> Reporter: Martin Ritchie
> Attachments: CloseAfterConnectionFailureTest.java, QPID-1779-SessionCloseBlockFix.patch
>
>
> Summary:
> When the connection is closed due to a network or protocol error attempting to cleanly shutdown the open objects will cause the client to block.
> Closing consumers will succeed as they have a default timeout of 30s.
> Closing a session uses -1 i.e. wait for ever, so will block the client code.
> Closing the connection uses a decreasing timeout is the only sure way of cleaning up.
> This however poses a problem for Mule users as their reconnection logic will be fired through the onException handler and explicitly close all the objects rather than just the connection.
> Test Case attached along with potential patch.
--
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