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

Robbie Gemmell updated QPID-3904:
---------------------------------

    Affects Version/s:     (was: 0.17)
        Fix Version/s: 0.17
    
> Java client should set AMQConnection#_closed flag on receipt of 0-10 
> connection.close
> -------------------------------------------------------------------------------------
>
>                 Key: QPID-3904
>                 URL: https://issues.apache.org/jira/browse/QPID-3904
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>            Reporter: Keith Wall
>            Assignee: Andrew MacBean
>             Fix For: 0.17
>
>
> If the broker closes the client's connection, you'd expect that future 
> attempts to use the client connection object would report an 
> IllegalStateException(""Object is closed") exception and 
> AMQConnection#isClosed to return true.
> However, the 0-10 client reports "Command was interrupted because of 
> failover, before being sent [error code 541: internal error]" and  
> AMQConnection#isClosed reports false.   This is confusing to the user.
> {code}
> javax.jms.JMSException: Error closing session: org.apache.qpid.AMQException: 
> Command was interrupted because of failover, before being sent [error code 
> 541: internal error]
> {code}
> It appears that the 0-10 client is current failing to flip the _closed atomic 
> in response to a receipt of a connection.close.  
> The problem does not affect 0-8..0-9-1.  Its users see an 
> IllegalStateException("Object has been closed") exception and 
> AMQConnection#isClosed returns true in this scenario.

--
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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to