You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Rainer Klute (JIRA)" <ji...@apache.org> on 2007/08/10 16:25:03 UTC

[jira] Commented: (AMQ-1095) Invalid messages selected from durable topic

    [ https://issues.apache.org/activemq/browse/AMQ-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39896 ] 

Rainer Klute commented on AMQ-1095:
-----------------------------------

I have developed a JUnit test case to verify this issue. The test cases show the following:
* The bug occurs only with durable subscribers. Non-durable subscribers work fine.
* The bug occurs if the ActiveMQ broker uses an already existing kaha directory. Everything works fine if the broker creates and uses a fresh kaha directory.


> Invalid messages selected from durable topic
> --------------------------------------------
>
>                 Key: AMQ-1095
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1095
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Selector
>    Affects Versions: 5.0.0
>            Reporter: Albert Strasheim
>            Assignee: Rob Davies
>         Attachments: ActiveMQ_Test.tar.bz2, DurableTopicSelector.java
>
>
> We think we've found an issue with durable topic subscriptions and message selectors.
> The attached application sends messages with an int property i with values 0..19 to a topic. We also have a durable subscription to the topic, selecting messages for which i%2=0. After sending the messages, the connection is started, allowing the consumer to receive the messages we've published that match the selection criterion. The second and every subsequent time we run the application, we see the following:
> message.i = 19
> message.i = 0
> message.i = 2
> message.i = 4
> message.i = 6
> message.i = 8
> message.i = 10
> message.i = 12
> message.i = 14
> message.i = 16
> message.i = 18
> message.i = 19 does not match the message selector criterion but it reaches our message handler anyway.
> Tested with ActiveMQ from trunk, revision 486090.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.