[
https://issues.apache.org/jira/browse/CXF-7023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15473707#comment-15473707
]
ASF GitHub Bot commented on CXF-7023:
-------------------------------------
GitHub user nikolobok opened a pull request:
https://github.com/apache/cxf/pull/166
[CXF-7023] JMS transport new parameter "oneSessionPerConnection" need…
…ed when using WMQ resource adapter
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nikolobok/cxf CXF-7023
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cxf/pull/166.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #166
----
commit a8b7fd5a8d23c0493a4c35941a76e0994525592a
Author: Nikolay Boklaschuk <boklasc...@yandex.ru>
Date: 2016-09-08T11:59:10Z
[CXF-7023] JMS transport new parameter "oneSessionPerConnection" needed
when using WMQ resource adapter
----
> 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
>
> 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.3.4#6332)
