activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Co (JIRA)" <>
Subject [jira] Commented: (AMQ-745) in message selector does not match messages
Date Thu, 15 Jun 2006 10:24:51 GMT
    [ ] 

Adrian Co commented on AMQ-745:


I tried to reproduce the issue, but the in selector seems to work using the browse command.
Im using the default out-of-the-box configuration. 
My test scenario includes:

1. start the default broker
2. run the producer example
3. run "browse --amqurl tcp://localhost:61616 TEST.FOO
4. Get a sample message ID
5. run "browse --amqurl tcp://localhost:61616 --msgsel "JMSMessageID='ID:Javacoola-1841-1150366504906-0:0:1:1:8'"
<one message is returned>
6. run "browse --amqurl tcp://localhost:61616 --msgsel "JMSMessageID IN ('ID:Javacoola-1841-1150366504906-0:0:1:1:8'")
<one message is returned>
7. run "browse --amqurl tcp://localhost:61616 --msgsel "JMSMessageID in ('ID:Javacoola-1841-1150366504906-0:0:1:1:8'")
<one message is returned>

Could you provide more details on your test method?

Maybe the message has been consumed/expired in between run?

Did you run the "browse --amqurl tcp://zuul:61616 --msgsel "JMSMessageID='ID:zuul-45732-1149587838616-3:24:1:1:1'"
queue:inbound" command after using IN to check if the message was still there?


Adrian Co

> in message selector does not match messages
> -------------------------------------------
>          Key: AMQ-745
>          URL:
>      Project: ActiveMQ
>         Type: Bug

>   Components: Selector
>     Versions: 4.0
>  Environment: Java 5.0 on Linux
>     Reporter: Jeff Martin
>     Assignee: Adrian Co

> Using "in" as part of a message selector does not return any messages.
> Example:
> This returns one message
> browse --amqurl tcp://zuul:61616 --msgsel "JMSMessageID='ID:zuul-45732-1149587838616-3:24:1:1:1'"
> This returns no messages
> browse --amqurl tcp://zuul:61616 --msgsel "JMSMessageID in ('ID:zuul-45732-1149587838616-3:24:1:1:1')"

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message