[
https://issues.apache.org/jira/browse/QPID-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Ritchie resolved QPID-826.
---------------------------------
Resolution: Fixed
Assignee: Martin Ritchie
When the connection is closed due to an Asynchronous error (see comment
QPID-805) the cause of the error is stored in the StateManager.
When a subsequent call is made on the session. Its call to validate the session
is still Open now checks to see if there is a cause attached in the
StateManager when the session is closed. If so then it wraps that error rather
than throwing the generic IllegalStateEx.
> Client does not report asynchronous exceptions from the broker through
> synchronous methods
> ------------------------------------------------------------------------------------------
>
> Key: QPID-826
> URL: https://issues.apache.org/jira/browse/QPID-826
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: M2.1
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: M3
>
>
> The SimpleACLTest is highlighting that any exception accompaning the
> connection close is not easily propogated to the client unless it happens to
> get to a Failover block of code before the close arrives.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
