[
https://issues.apache.org/jira/browse/QPID-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14052508#comment-14052508
]
Rajith Attapattu commented on QPID-5868:
----------------------------------------
Apologies for not putting enough info in the JIRA.
Robbie you description is correct.
If an execution exception is thrown at the time close is initiated you can
easily reproduce this issue.
When notified of the exception the AMQSession_0_10 tries to close the session.
However the thread is blocked waiting to grab the message delivery lock. But
that lock is already taken by the thread that initiated the close and is
blocked (timed wait) on the commandsLock waiting for the sync to complete.
Once it times out, and since the session is still not closed, the exception
being thrown is the time out exception and not the exception that caused the
session close.
> Java client ignores exceptions when waiting on sync
> ---------------------------------------------------
>
> Key: QPID-5868
> URL: https://issues.apache.org/jira/browse/QPID-5868
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.27
> Reporter: Rajith Attapattu
> Fix For: 0.29
>
> Attachments: QPID-5868.patch
>
>
> The java client will wait on the sync command even if an execution exception
> is received from the broker.
> It will then proceed to throw a timeout exception and the execution exception
> is not reported properly to the application.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
