You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2011/09/23 15:50:26 UTC
[jira] [Resolved] (CAMEL-4240) Unable to use XA JMS trabsaction on
WebLogic
[ https://issues.apache.org/jira/browse/CAMEL-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-4240.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.8.2
Thanks. I applied the light patch.
> Unable to use XA JMS trabsaction on WebLogic
> --------------------------------------------
>
> Key: CAMEL-4240
> URL: https://issues.apache.org/jira/browse/CAMEL-4240
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
> Reporter: Andrey Utkin
> Assignee: Claus Ibsen
> Fix For: 2.8.2, 2.9.0
>
> Attachments: camel-jms-r1173278-CAMEL-4240-light.diff, camel-jms-r1173278-CAMEL-4240.diff
>
>
> There is problem with camel-jms component deployed on WebLogic 10.3.X and XA connection factory.
> As spring developers suggests, if we use XA transaction on WebLogic we must set SessionTransacted to false and specify transactionManager. See http://ourcraft.wordpress.com/2008/10/22/the-mysteriously-necessary-sessiontransactedtrue/ comment #9 by Juergen Hoeller.
> But camel-jms setup transactionManager for MessageListener only when "transacted" property is true. So, it is not possible to use XA transactions with WebLogic JMS.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira