[
https://issues.apache.org/jira/browse/CXF-7023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16289204#comment-16289204
]
Simon Marti commented on CXF-7023:
----------------------------------
I am currently in the process of updating nikolobok's changes for the current
{{master}} branch and will submit a new pull request as soon as I had a chance
to properly test the changes.
We are already running a patched version
([https://github.com/inventage/cxf/commits/CXF-7023-3.1.10]) of CXF 3.1.10 in a
testing environment and have not encountered any issues this far. Eventually
this patch might result in a pull request on the {{3.1.x-fixes}} branch.
> SOAP over JMS transport does not use XA transactions with Websphere MQ
> resource adapter
> ---------------------------------------------------------------------------------------
>
> Key: CXF-7023
> URL: https://issues.apache.org/jira/browse/CXF-7023
> Project: CXF
> Issue Type: Bug
> Components: JMS
> Affects Versions: 3.1.7
> Reporter: Nikolay Boklaschuk
> Assignee: Christian Schneider
>
> When using Websphere MQ resource adapter
> Inbound one-way service does not uses XA transactions.
> This is because WMQ adapter decides to use XA transaction when creates jms
> connection, but connection opened in JMSDestination, and transaction started
> in PollingMessageListnerContainer after connection created.
> Futhermore WMQ adapter holds only one session per connection.
> I have patched XAPoller to hold connection for each thread, it works, but may
> be there are better way to provide support for WMQ adapter?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
