Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <538265255.1248359433831.JavaMail.jira@brutus>
Date: Thu, 23 Jul 2009 07:30:33 -0700 (PDT)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Resolved: (AMQCPP-256) Transaction has not been started
 exceptions on the broker with parallel transacted sessions
In-Reply-To: <1222098965.1248195514431.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/activemq/browse/AMQCPP-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQCPP-256.
---------------------------------

    Resolution: Fixed

Resolved in trunk.

Unfortunately the fix breaks binary compatibility so it won't make it into a 3.0.2 release but will have to wait for a 3.1 release.

> Transaction has not been started exceptions on the broker with parallel transacted sessions
> -------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-256
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-256
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    Affects Versions: 3.0
>         Environment: Ubuntu Jaunty 9.04
>            Reporter: Teemu Torma
>            Assignee: Timothy Bish
>            Priority: Critical
>             Fix For: 3.1
>
>         Attachments: mt-receive.cpp
>
>
> When using parallel transacted sessions and consumers to same queue each sharing the same connection, the messages are delivered but the broker 5.2 gets exceptions
> javax.jms.JMSException: Transaction 'TX:de411476-d65d-fff7-1e84-be7c9abd80b5:6' has not been started.
> and some messages are left on the broker even though they were delivered.
> The issue seems to be related to multi-threading, by protecting each receive/commit with a lock the error does not happen.  I am sorry I don't have a test program ready, but it should be easy to reproduce by creating multiple transacted session threads with prefetchSize=1 and consuming messages, commiting after each message.  I have seen this happen both with consumers and listeners.

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