Rajith has a client re-factor on the branch, you might want to connect with him as all the JMS stuff is in the client.

Carl.


Tejeswar Das (JIRA) wrote:
     [ 
https://issues.apache.org/jira/browse/QPID-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tejeswar Das reassigned QPID-432:
---------------------------------

    Assignee: Tejeswar Das

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

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?


Reply via email to