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 2007/04/23 13:24:17 UTC
[jira] Updated: (QPID-432) Client Code doesn't correctly close a
JMSSession/Channel when the broker demands it.
[ https://issues.apache.org/jira/browse/QPID-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-432:
--------------------------------
Fix Version/s: M3
> Client Code doesn't correctly close a JMSSession/Channel when the broker demands it.
> ------------------------------------------------------------------------------------
>
> Key: QPID-432
> URL: https://issues.apache.org/jira/browse/QPID-432
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Reporter: Martin Ritchie
> Assigned To: Tejeswar Das
> Fix For: M3
>
>
> When a Channel exception occurs the Java client propogates the error but doesn't remove the JMSSession mapping from the connection so when connection.close is called the already closed AMQP-Channel is closed again.. resulting in a ConnectionException.
> See AMQProtocolSession for where the execption is progogated and ignored
> See Also ChannelCloseException for where the session is only removed from the map when a channel close is received with error code REPLY_SUCCESS other wise it thows an exception before calling this code.. should the code be in a finally?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.