[
https://issues.apache.org/jira/browse/QPID-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14052722#comment-14052722
]
Rajith Attapattu commented on QPID-5868:
----------------------------------------
I verified that both the transport session and the AMQSession_0_10 (jms
session) are both marked closed by the time the exception is thrown to the
application, which I think is the most important thing.
Both the sync method and the exception method (called via the listener
interface) delegates to setCurrentException method.
Therefore which gets called first doesn't matter.
Without the patch, important exceptions are not reported and customers have
complained about it.
Therefore I believe it's important to get this patch in.
> 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
