activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rainer Klute (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-1095) Invalid messages selected from durable topic
Date Tue, 14 Aug 2007 10:07:22 GMT

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

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

I am one step further now: It might be disputed whether it is sensible or not to add messages
to all topic subscribers. However, that does obviously no harm when a fresh kaha store is
used.

However, when a kaha store is recovered that had been created in a former run, the messages
that went to the wrong subscribers are still in the store. But now they show up at all subscribers
independed of their selectors.

> 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.


Mime
View raw message