[
https://issues.apache.org/jira/browse/QPID-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593347#comment-13593347
]
Robbie Gemmell commented on QPID-4617:
--------------------------------------
This seems like a good final check to make to stop the non-null ReplyTo object
from causing the wrong value to be returned, but it doesn't seem to me that it
fixes the real underlying issue: why does the client have a non-null ReplyTo
object, i.e think there was a reply-to set when there wasn't?
I think its worth looking into that, as it implies either an issue further down
inside the transport code, that the client is actually sending the wrong
information to the broker originally, or the broker is sending the wrong
information back to the client. Identifying which of these it is and rectifying
that might even allow for resolving this issue for older version clients when
they are interacting with the newer clients/brokers, rather than confining the
workaround to only consumers using the new client.
(P.S. was there a reason not to use the original JIRA with Pavel's patch
attached to it? Or to not fully update either one after the commit?)
> getJMSReplyTo does not return null for when ReplyTo property is empty
> ---------------------------------------------------------------------
>
> Key: QPID-4617
> URL: https://issues.apache.org/jira/browse/QPID-4617
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Priority: Minor
> Fix For: 0.21
>
>
> If the replyTo property is not set or explicitly set to null, on the receiver
> side, getJMSReplyTo should return null.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
