On Tue, 2009-07-21 at 14:10 -0700, RakeshRay wrote: > I am facing exactly same issue in 5.2. >
Are you using a CPP client or a Java client? Regards Tim. > > > JIRA [email protected] wrote: > > > > 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 > > > > > > 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. > > > > > > > -- Tim Bish http://fusesource.com http://timbish.blogspot.com/
