You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/02/26 12:29:00 UTC
[jira] [Commented] (AMQ-4486)
ActiveMQResourceAdapter.getXARessources() broken
[ https://issues.apache.org/jira/browse/AMQ-4486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777865#comment-16777865 ]
ASF subversion and git services commented on AMQ-4486:
------------------------------------------------------
Commit 5bd2abf85dbda14bf41f54d09af4866e814f931f in activemq's branch refs/heads/master from gtully
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=5bd2abf ]
AMQ-5790 - rework the fix from AMQ-4486 to tie the inbound xaResource connection lifectyle to the rar start/stop
> ActiveMQResourceAdapter.getXARessources() broken
> ------------------------------------------------
>
> Key: AMQ-4486
> URL: https://issues.apache.org/jira/browse/AMQ-4486
> Project: ActiveMQ
> Issue Type: Bug
> Components: JCA Container
> Affects Versions: 5.8.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 5.9.1, 5.10.0
>
>
> The Implementation of ActiveMQResourceAdapter.getXAResources() is broken.
> Its internal call to makeConnection() creates a non-XA ActiveMQConnectionFactory which is then discarded as this ConnectionFactory is not XA-aware. As a result an empty XAResources array is returned.
> This causes transaction recovery in the application server to fail.
> Where the resource adapter can be manually configured (with beans for example) it is possible to work around by injecting the connection factory as an XA aware variant.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)