qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPIDJMS-93) Extract proper error from Rejected disposition to avoid NPE as cause of a JMSException
Date Wed, 19 Aug 2015 22:09:45 GMT

    [ https://issues.apache.org/jira/browse/QPIDJMS-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14703826#comment-14703826

ASF subversion and git services commented on QPIDJMS-93:

Commit 776de4c25a177780c4a65a13b7992234ccd6c0a6 in qpid-jms's branch refs/heads/master from
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=776de4c ]


Add an additional test for the sync send case. 

> Extract proper error from Rejected disposition to avoid NPE as cause of a JMSException
> --------------------------------------------------------------------------------------
>                 Key: QPIDJMS-93
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-93
>             Project: Qpid JMS
>          Issue Type: Bug
>          Components: qpid-jms-client
>    Affects Versions: 0.1.0, 0.2.0, 0.3.0, 0.4.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 0.5.0
> When an send is answered with a Rejected disposition we don't try to extract the error
from the outcome and this result in no Exception being propagated up to the exception dispatcher
which leads to an NPE getting set into the JMSException we fire.  
> This also impacts error detection when the connection is set to always sync send and
a broker like ActiveMQ sends back an error on a send.  Without the outcome error lookup we
fail to properly throw a JMSException from a failed send because the error value that propagates
up is null.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message