You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2015/08/19 23:56:46 UTC
[jira] [Updated] (QPIDJMS-93) Extract proper error from Rejected
disposition to avoid NPE as cause of a JMSException
[ https://issues.apache.org/jira/browse/QPIDJMS-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish updated QPIDJMS-93:
--------------------------------
Description:
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.
was: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.
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org