[
https://issues.apache.org/jira/browse/QPID-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-2723:
-----------------------------------
Attachment: QPID-2723.patch
This contains a patch that fixes the issue mentioned here.
However the fix needs the session reference to be valid in order to perform the
lookups.
However the code in AMQMessageDelegate_0_10 and AMQMessageDelegate_0_8 relies
on the session being null to figure out if the ack mode is CLIENT_ACK in the
acknowledge method.
I am not sure if this is a correct assumption to make as somebody could easily
violate this.
Therefore I changed the code to check the ack mode explicitly.
I am also setting a valid session reference to every message irrespective of
the ack mode.
> NullPointerException thrown when you pass an address based destination to the
> setJMSReplyTo() in a Message.
> -----------------------------------------------------------------------------------------------------------
>
> Key: QPID-2723
> URL: https://issues.apache.org/jira/browse/QPID-2723
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 0.7
>
> Attachments: QPID-2723.patch
>
>
> When you pass a destination which was not used in consumer / producer (even
> when the address was the same, only the object was different), a
> NullPointerException is thrown, because the getExchangeName and getRoutingKey
> methods from AMQDestination returns null. This is due to a address not being
> evaluated properly and the details not being extracted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
