Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <1809882473.1212583380324.JavaMail.jira@brutus>
Date: Wed, 4 Jun 2008 05:43:00 -0700 (PDT)
From: "Kevin (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Created: (AMQ-1767) Multiple creating and closing consumers
 causes messages duplicated delivered
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Multiple creating and closing consumers causes messages duplicated delivered
----------------------------------------------------------------------------

                 Key: AMQ-1767
                 URL: https://issues.apache.org/activemq/browse/AMQ-1767
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.1.0
         Environment: Windows XP, Java 1.5
            Reporter: Kevin
         Attachments: JUnit.zip

Hi *,

I'm running AcitveMQ 5.1 in a VM. The broker is set as persistent with amq-store, the xml-configuration-file is attached (in the zip-file).

One MessageProducer sends 10.000 messages to a queue. The producers runs in its own thread with its own session.

The queue is set as transacted.

Two MessageConsumers register on the queue mentioned above, each in its own thread with its own session.

The Producer and the Consumers share one connection-object.

Every second one Consumer is called to be canceld (by session.close - a call to consumer.close does not help), its thread is stopped and a new Consumer is created in a new thread with its own session.

What happens?
1 to 10 messages are duplicated delivered from some consumers. So the 'EnqueueCount' is greater than the 'DequeueCount'. E.G. 10.002 messages are recieved, but just 10.000 messages are sent.

I've tried to synchronized by one common-object the creating, closing or commiting in the Consumer with no success.

Attached is a junit-test, which demonstrates the situation. Before have a look at the Config-Class and change the ip-address, where your broker runs.

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