[
https://issues.apache.org/jira/browse/QPID-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell reopened QPID-3233:
----------------------------------
> In some cases the JMS Session does not get notified of the AMQP session
> closed, due to an execution exception received from the broker.
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-3233
> URL: https://issues.apache.org/jira/browse/QPID-3233
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.10
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 0.12
>
>
> If the JMS client receives an execution exception asynchronously it will not
> notify the JMS Session (AMQSession_0_10.java) object.
> Therefore the JMS Session remains opened while the underlying AMQP session
> was closed.
> Any subsequent operation that only relies on the check "checkNotClosed()"
> will not throw an exception.
> Ex. Creating a producer with an already resolved destination or creating
> messages (ex. session.createTextMessage()).
> The JMS session will only throw an exception if only a call is delegated to
> the underlying AMQ session class.
> We should also ensure that when the JMS Session gets notified about the
> underlying session being closed, it should also keep information about the
> exception that caused it.
> This exception should then be included in the JMS Exception that gets thrown
> in a subsequent operation due to the JMS Session being closed.
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
