cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Müller (JIRA) <j...@apache.org>
Subject [jira] [Comment Edited] (CXF-7023) SOAP over JMS transport does not use XA transactions with Websphere MQ resource adapter
Date Fri, 21 Oct 2016 07:29:58 GMT

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

Rainer Müller edited comment on CXF-7023 at 10/21/16 7:29 AM:
--------------------------------------------------------------

Patch fixed our issue with WebSphere MQ Resource Adapter 7.5.0.5 running in JBoss EAP 7.0.2.GA
and Apache CXF version 3.1.6.

Any plans when the fix will be release with Apache CXF?

Closed the duplicate issue CXF-7094.


was (Author: rainer.mueller):
Patch fixed our issue with WebSphere MQ Resource Adapter running in JBoss EAP 7.0.2.GA and
Apache CXF version 3.1.6.

Any plans when the fix will be release with Apache CXF?

Closed the duplicate issue CXF-7094.

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

Mime
View raw message