Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <18539794.1187019322399.JavaMail.jira@brutus>
Date: Mon, 13 Aug 2007 08:35:22 -0700 (PDT)
From: "Rainer Klute (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-1095) Invalid messages selected from durable
 topic
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


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

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

It seems to me that the bug is in the Kaha persistence manager namely in the method org.apache.activemq.store.kahadaptor.KahaTopicMessageStore.addMessage(ConnectionContext context, Message message). Here the message is added to the message containers of *all* topic subcribers without checking their respective selectors. Am I on the right track here or not?

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