qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-3289) Session exceptions should only be notified via the exception listener, if it cannot be thrown directly to the application.
Date Sun, 26 Feb 2012 21:46:49 GMT

     [ https://issues.apache.org/jira/browse/QPID-3289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robbie Gemmell updated QPID-3289:
---------------------------------

    Component/s: Java Client
    
> Session exceptions should only be notified via the exception listener, if it cannot be
thrown directly to the application.
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-3289
>                 URL: https://issues.apache.org/jira/browse/QPID-3289
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>            Reporter: Rajith Attapattu
>            Assignee: Rajith Attapattu
>
> The 0-10 code path in the JMS client always notifies a session exception via the connection
listener, even when it can throw a JMS exception for a synchronous method call.
> For example session.createConsumer(destination) could fail due to an ACL violation and
the session gets closed with an execution exception.
> Currently the JMS client throws an exception and also notifies the connection listener
which results in the connection (and any other sessions associated with that connection) being
closed.
> Another undesirable effect of this is the potential for deadlocks happening around the
failovermutex.
> A reasonable solution for this problem would be to not notify via the connection listener
if there is a way of throwing an exception to the application directly.
> For example session.createConsumer/Producer is a synchronous call and we could easily
throw a JMS exception. In this case there is little value in notifying this via the connection
listener and it also has the undesirable effect of closing the connection.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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-subscribe@qpid.apache.org


Mime
View raw message