Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <10456764.1190988863990.JavaMail.jira@brutus>
Date: Fri, 28 Sep 2007 07:14:23 -0700 (PDT)
From: "Hiram Chirino (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_40218 ] 

Hiram Chirino commented on AMQ-1095:
------------------------------------

Hi Klute,

is it just the attached DurableTopicSelector.java that I need to verify the bug??  Could you reattach with an Apache License header on it and make sure you click the check box that says your contributing to the ASF.

Thanks.

> 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: Hiram Chirino
>             Fix For: 5.2.0
>
>         Attachments: ActiveMQ_Testcases.jar, DurableTopicSelector.java, patch_for_AMQ-1095.diff
>
>
> 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.