Thx Gtully , I applied this patch and this problem was fixed
Regards
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-XA-JBoss-6-1-problem-tp4670555p4670735.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
if you can patch ActiveMQSession that will do it.
Apply this change:
http://svn.apache.org/viewvc/activemq/trunk/activemq-client/src/main/java/org/apache/activemq/ActiveMQSession.java?r1=1504279&r2=1504278&pathrev=1504279
On 21 August 2013 17:21, juanlopez wrote:
> Hi I have the same problem in t
Issue: https://issues.apache.org/jira/browse/AMQ-4634
Resolved
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-XA-JBoss-6-1-problem-tp4669324p4669473.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ActiveMQSession creates a new local transaction because there isn't an XA trx
in the trasactioncontext.
Logs:
/09:22:32,326 DEBUG [org.apache.activemq.TransactionContext] Start: <
formatId=131076, gtrid_length=29, bqual_length=28,
tx_uid=0:c0a80ad8:126a:51e5393b:43, node_name=1,
branch_uid=0:f
I've tried to reproduce this without calling the stateless ejb but it works
well.
The ActiveMQSession class should retain the original transactionContext, as
you mentioned.
I'll create an issue.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-XA-JBoss-6-1-problem
btw: in the jboss logs or on the console, do you see:
WARN [org.apache.activemq.ra.ServerSessionImpl:0]
(default-threads - 2) Local transaction had not been commited.
Commiting now.
On 15 July 2013 21:10, gastonscapusio wrote:
> Hi,
> We have some XA problems using ActiveMQ ra within Jbos
this is a bug for sure. I came across the same thing yesterday and am
investigating. I think the problem can also happen independent of the
call to a stateless ejb. It is an issue with the session auto ack
level and the absence of a transaction context after an abort due to a
timeout.
It looks like
