activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject activemqcpp, stomp and openwire and message selectors
Date Tue, 12 Oct 2010 11:43:45 GMT

I have just been nobbled by some activemqcpp behaviour that only seems to 
apply when STOMP is being used with message selectors. It is the 
restriction that message selector applies to a session, not to individual 
messages. I am truly amazed at this. Luckily I found it documented at Well, this 
documented behaviour is what I found the hard way. At least, maybe....

What was puzzling is why it seemed to be using STOMP. It was not specified 
in the URL. Preliminary experiments also seemed to give the same behaviour 
when using openwire (by adding ?wireFormat=openwire to the URL).

Can anyone shed more light on this please? Has anyone managed to use 
message selectors with AMQCPP?


Andrew Marlow

This e-mail may contain confidential and/or privileged information. If you are not the intended
recipient (or have received this e-mail in error) please notify the sender immediately and
delete this e-mail. Any unauthorised copying, disclosure or distribution of the material in
this e-mail is prohibited.

Please refer to
 for additional disclosures.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message