On 05/24/2016 02:07 AM, Vavricka wrote:
tabish...@gmail.com wrote
The broker won't be able to select on the MessageID as the AMQP message
ID is foreign to the broker and it must create its own internal instance
in order to properly function so the ID the client assigns wouldn't
match what the real broker side message has as its ID.
Message is instance of javax.jms.Message. So the JMS Message ID and
JMSMessageID selector is also foreign to the Artemis broker?
Not entirely sure how Artemis handles the message ID on the messages it
receives so I can't say for sure if it will apply the JMS selector and
get a match on the message IDs.
The question regarding AMQP filtering was meant if AMQP selectors are
supported (like amqp.message_id, amqp.creation_time)? It has nothing to do
with JMS selectors (like JMSMessageID, JMSTimestamp).
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JMSMessageID-filtering-tp4712257p4712297.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ActiveMQ 5.x doesn't implement an AMQP based selector filter you would
need to use the standard JMS message selector syntax and treat the
messages as JMS messages so you'd select on JMSTimeStamp etc, Artemis
is the same as far as I know.
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
