[
https://issues.apache.org/jira/browse/CXF-7023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15594239#comment-15594239
]
Nikolay Boklaschuk commented on CXF-7023:
-----------------------------------------
Glad to see that my patch come useful for you.
There is no any response from cxf team, so I am waiting.
One more thing: the whole jms transport implementation not good because based
on pooling.
There is outdated implementation by Benoit from OW2 JOnAS project based on mdb.
But I did not tried it, because our project has been stopped.
I think it could be merged in mainline with some improvements alongside with
current transport.
> 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)
