[rabbitmq-discuss] When using rabbitmq-jms javax.jms.Message.getJMSDestination does not return the actual destination when it is received from a consumer listening on a Topic with a wild card

Thu Dec 12 22:21:01 GMT 2013

Found out why: the fix went into 1.0.6, which is why it doesn't appear in the 1.1.0 notes.
This was a small fix release, the last in the 1.0.x series.

Steve Powell  [M: +44-7815-838-558; H:+44-1962-775-598; W:+44-2380-111-528]
    What I tell you three times is true.
Lewis Carroll; Hunting of the Snark: Fit the First

On 12 Dec 2013, at 22:16, Steve Powell <steve at rabbitmq.com> wrote:

> You are right, it isn't in the release notes -- I wonder why? But the fix is in RJMS 1.1.0, certainly. Sorry for misleading you.
> Steve Powell  [M: +44-7815-838-558; H:+44-1962-775-598; W:+44-2380-111-528]
>     And you all know, security is mortals’ chiefest enemy.
> Macbeth: III, 5
> 
> Steve Powell  [M: +44-7815-838-558; H:+44-1962-775-598; W:+44-2380-111-528]
>     What I tell you three times is true.
> Lewis Carroll; Hunting of the Snark: Fit the First
> 
> On 10 Dec 2013, at 19:36, Josh Carlson <josh.carlson at kaazing.com> wrote:
> 
>> Hi Steve,
>> 
>> I was wondering if this fix appears in the 1.1 client? It doesn't appear to be in the release notes https://www.vmware.com/support/vfabric-rabbitmq/doc/vfabric-rabbitmq-rn-3.2.html#resolvedissues-rjms
>> 
>> Thanks
>> 
>> Josh
>> 
>> On 09/18/2013 06:57 AM, Steve Powell wrote:
>>> Thanks Josh,
>>> 
>>> This indeed appears to be a bug.  [I go to the trouble of serialising and deserializing the destination and then overwrite it with the Consumer’s destination before returning it!]
>>> 
>>> I will raise an internal bug and should have this corrected in the next release. Should you require further support this should be requested through the usual vFabric channels.
>>> 
>>> Steve Powell  [Cell: +44-7815-838-558] [RabbitMQ, Pivotal]
>>> “L’enfer, c’est les autres.” Sartre
>>> 
>>> On 17 Sep 2013, at 20:21, Josh Carlson <josh.carlson at kaazing.com> wrote:
>>> 
>>>> When using rabbitmq-jms for vFabric RabbitMQ javax.jms.Message.getJMSDestination does not return the actual destination when it is received from a consumer listening on a Topic with a wild card. I have tested with both 1.0.3 and 1.0.5 clients with RabbitMQ 3.1.5.
>>> 
>> 
> 
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131212/995534a8/attachment.html>