[
https://issues.apache.org/activemq/browse/AMQ-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56130#action_56130
]
Gary Tully commented on AMQ-2514:
---------------------------------
post your spring xml here also, it may help to tie it together. Did you notice:
"NOTE: Turn off the "cacheSessions" flag on JBoss 4.0 to make JMS message
reception properly participate in XA transactions, where JBoss requires each
listener thread to reobtain its JMS Session for each receive attempt." from
http://www.jdocs.com/spring/2.0.RC1/org/springframework/jms/listener/DefaultMessageListenerContainer.html
- wonder if that is relevant.
> xa jta activemq jboss - xa transaction not set in session
> ---------------------------------------------------------
>
> Key: AMQ-2514
> URL: https://issues.apache.org/activemq/browse/AMQ-2514
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.3.0
> Environment: JBossTS 4.2.3 SP5, activemq 5.3.0, jdk1.6.0_16, winxp,
> spring 2.5.6, hp desktop
> Reporter: Miten Mehta
>
> JBoss based global transaction does not work with active mq. The session for
> say jms though is ActiveMQXASession getting created but its transaction
> related values are not set at all due to which even after retrieving the
> message it fails after doing check for whether its transaction context is set
> or not. It will give JMS Exception as "Session's XAResource has not been
> enlisted in a distributed transaction.".
> You can find the thread on nabble at:
> http://old.nabble.com/xa-jta-activemq-jboss-td26515685.html#a26527052
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
