You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2011/08/22 01:34:29 UTC
[jira] [Updated] (QPID-3440) the Destination cache in
AMQMessageDelegate_0_10 does not work
[ https://issues.apache.org/jira/browse/QPID-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPID-3440:
---------------------------------
Attachment: QPID-3440_wip.patch
Attaching an initial patch, with test to verify the issue and addition of equals() and hashCode() methods to the generated file causing the problem.
Not yet applied becuase doing so breaks PropertyValueTest. This is due to failing a Destination equality test, despite the fact the toString of the destinations is actually the same (which it wasnt before), but the equals check fails because of a change in underlying object in use, due to the horrible number of different objects and ways to instantiate them in our wonderfully dispirate Destination handling.
> the Destination cache in AMQMessageDelegate_0_10 does not work
> --------------------------------------------------------------
>
> Key: QPID-3440
> URL: https://issues.apache.org/jira/browse/QPID-3440
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.6, 0.7, 0.8, 0.9, 0.10, 0.11, 0.12
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.13
>
> Attachments: QPID-3440_wip.patch
>
>
> The Destination cache in AMQMessageDelegate_0_10 does not work, because it indexes the cache by the underlying ReplyTo transport class, which has no equals() implementation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org