[
https://issues.apache.org/jira/browse/CXF-7023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977240#comment-15977240
]
Nikolay Boklaschuk commented on CXF-7023:
-----------------------------------------
As I can remember, it only holds one session per connection, there could be
many connections but only with one session in each, so there will be the same
count of simultaneously threads how many connections is.
One thread can dispatch only one message (or packet) in time, but it should not
close a connection after each message as i can remember.
There is no another way to use wmq brand adaptor.
And it not makes code or architecture more complecated, just cuts some
multitasking when turned on.
The commit has been done for a half a year ago, and was fully working.
May be it needs some merge for now.
> 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.3.15#6346)
