[QPID-3636] getJMSReplyTo does not return null for null ReplyTo property

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.12
• Component/s: JMS AMQP 0-x
• Labels: addressing jms-compliance
• Assignee: Unassigned
• Reporter: Pavel Moravec
• Created: 21/Nov/11 17:43
• Updated: 05/Mar/13 22:27
• Resolved: 05/Mar/13 22:27

Description

Description of problem:
Java client library wrongly returns reply-to via Message::getJMSReplyTo method
for a message with setJMSReplyTo(null) called before.

How reproducible:
100%

Steps to Reproduce:
Use attached JUnit test. In short, the test performs:
1. msg.setJMSReplyTo(null);
2. producer.send(msg);
3. msg = consumer.receive();
4. msg.getJMSReplyTo() now returns:
:////?routingkey=''

Actual results:
msg.getJMSReplyTo() now returns:
:////?routingkey=''

Expected results:
msg.getJMSReplyTo() should return null

Additional info:
The root cause of the bug is in calling:

AMQMessageDelegate_0_10.java:

public Destination getJMSReplyTo()
{
ReplyTo replyTo = _messageProps.getReplyTo();

if (replyTo == null)

{ return null; }

else
{

The _messageProps.getReplyTo() does not return null but "ReplyTo()".

Issue Links

• is duplicated by: QPID-4617 getJMSReplyTo does not return null for when ReplyTo property is empty