You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2014/01/21 15:00:20 UTC
[jira] [Reopened] (AMQ-4486)
ActiveMQResourceAdapter.getXARessources() broken
[ https://issues.apache.org/jira/browse/AMQ-4486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully reopened AMQ-4486:
-----------------------------
Assignee: (was: Gary Tully)
leaving connections hanging about till finalize won't cut it with fd limits etc.
need to have a resource wrapper that will open/close a connection for every xa operation.
> 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
> Fix For: 5.9.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
(v6.1.5#6160)