You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Teemu Torma (JIRA)" <ji...@apache.org> on 2009/07/21 18:58:34 UTC
[jira] Created: (AMQCPP-256) Transaction has not been started
exceptions on the broker with parallel transacted sessions
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.
Re: [jira] Created: (AMQCPP-256) Transaction has not been started
exceptions on the broker with parallel transacted sessions
Posted by Timothy Bish <ta...@gmail.com>.
On Tue, 2009-07-21 at 14:28 -0700, RakeshRay wrote:
> I am using Perl client. I guess, if there is an issue with broker, it will be
> reproducable, no matter what transport is used!
>
Ok, so you are using stomp them as the Wire Format. This sort of info
helps us at least narrow in a bit on where the problem might be.
Regards
Tim.
>
> Timothy Bish wrote:
> >
> > 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 jira@apache.org 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/
> >
> >
> >
> >
> >
>
Re: [jira] Created: (AMQCPP-256) Transaction has not been started
exceptions on the broker with parallel transacted sessions
Posted by RakeshRay <Ra...@Proquest.com>.
I am using Perl client. I guess, if there is an issue with broker, it will be
reproducable, no matter what transport is used!
Timothy Bish wrote:
>
> 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 jira@apache.org 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/
>
>
>
>
>
--
View this message in context: http://www.nabble.com/-jira--Created%3A-%28AMQCPP-256%29-Transaction-has-not-been-started-exceptions-on-the-broker-with-parallel-transacted-sessions-tp24591610p24596191.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: [jira] Created: (AMQCPP-256) Transaction has not been started
exceptions on the broker with parallel transacted sessions
Posted by Timothy Bish <ta...@gmail.com>.
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 jira@apache.org 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/
Re: [jira] Created: (AMQCPP-256) Transaction has not been started
exceptions on the broker with parallel transacted sessions
Posted by RakeshRay <Ra...@Proquest.com>.
I am facing exactly same issue in 5.2.
JIRA jira@apache.org 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.
>
>
>
--
View this message in context: http://www.nabble.com/-jira--Created%3A-%28AMQCPP-256%29-Transaction-has-not-been-started-exceptions-on-the-broker-with-parallel-transacted-sessions-tp24591610p24595909.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] Commented: (AMQCPP-256) Transaction has not been started
exceptions on the broker with parallel transacted sessions
Posted by "Teemu Torma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52887#action_52887 ]
Teemu Torma commented on AMQCPP-256:
------------------------------------
I should mention that the problem does not happen with activemq-cpp 2.2
> 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.
[jira] Closed: (AMQCPP-256) Transaction has not been started
exceptions on the broker with parallel transacted sessions
Posted by "Teemu Torma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Teemu Torma closed AMQCPP-256.
------------------------------
Seems to work when applied to 3.0.1.
> 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.
[jira] Commented: (AMQCPP-256) Transaction has not been started
exceptions on the broker with parallel transacted sessions
Posted by "Teemu Torma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52890#action_52890 ]
Teemu Torma commented on AMQCPP-256:
------------------------------------
Some general observations:
- Using the same concept with message listener fails the same way.
- Without any delay in message processing the problem is very hard to reproduce.
- Using CLIENT_ACKNOWLEDGE works.
- Synchronizing the message receiving and commit makes the problem go away, but that is not really multi-threaded.
For me it sounds that something in activemq-cpp transaction managements gets confused based on timing of receiving the message and the commit. I might be wrong though.
> 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
> 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.
[jira] Resolved: (AMQCPP-256) Transaction has not been started
exceptions on the broker with parallel transacted sessions
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (AMQCPP-256) Transaction has not been started
exceptions on the broker with parallel transacted sessions
Posted by "Teemu Torma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Teemu Torma updated AMQCPP-256:
-------------------------------
Attachment: mt-receive.cpp
Here is a test program, I hope it is clear enough. I haven't tried with 5.3, but even with 5.2 this works with activemq-cpp 2.2.
The usage is to send let's say 100 messages to queue FOO and then run the program. What I see is broker exceptions and even if I receive exactly 100 messages, something might be left at the server.
The behaviour is a bit random and may not be reproducible at every run, but currently this fails for me every time if there are 100 messages in the queue at localhost.
> 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
> 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.
[jira] Updated: (AMQCPP-256) Transaction has not been started
exceptions on the broker with parallel transacted sessions
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish updated AMQCPP-256:
--------------------------------
Fix Version/s: 3.1
> 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.
[jira] Commented: (AMQCPP-256) Transaction has not been started
exceptions on the broker with parallel transacted sessions
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52899#action_52899 ]
Timothy Bish commented on AMQCPP-256:
-------------------------------------
I gave this a shot this morning, I can confirm that its reproducible with the 5.3 SNAPSHOT as well.
> 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
> 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.
[jira] Commented: (AMQCPP-256) Transaction has not been started
exceptions on the broker with parallel transacted sessions
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52888#action_52888 ]
Timothy Bish commented on AMQCPP-256:
-------------------------------------
A test would definitely help to understand exactly what you are doing when the error occurs.
Are you using the default openwire wire format or are you using stomp?
Have you tried the same code using the latest ActiveMQ 5.3 SNAPSHOT?
> 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.