You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2017/04/20 15:38:04 UTC

[jira] [Commented] (CXF-7023) SOAP over JMS transport does not use XA transactions with Websphere MQ resource adapter

    [ https://issues.apache.org/jira/browse/CXF-7023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976911#comment-15976911 ] 

Christian Schneider commented on CXF-7023:
------------------------------------------

If I understand the PR correctly then it is creating a new connection for every received message. Is that really necessary for WMQ?
This makes the whole code a lot more complicated. I would really like to avoid this.

I wonder if there is some documentation about this behaviour. Maybe WMQ can be used in a different way to behave more like the other providers.




> 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)