You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2017/10/30 16:18:00 UTC

[jira] [Commented] (ARTEMIS-1487) Resource Adapter should use TransactionSynchronizationRegistry instead of TransactionManager

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

Justin Bertram commented on ARTEMIS-1487:
-----------------------------------------

FWIW, the [{{getTransactionSynchronizationRegistry()}}|https://docs.oracle.com/javaee/6/api/javax/resource/spi/BootstrapContext.html#getTransactionSynchronizationRegistry()] method was added in JCA 1.6 and the Artemis RA is JCA 1.5.

> Resource Adapter should use TransactionSynchronizationRegistry instead of TransactionManager
> --------------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-1487
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1487
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.3.0
>            Reporter: Sami Korhonen
>            Priority: Minor
>
> Resource Adapter (artemis-ra) is currently using TransactionManager using application server specific locators (TransactionManagerLocator). On Java EE application servers Resource Adapter should use TransactionSynchronizationRegistry provided in BootstrapContext. JTA transaction timeouts should be controlled by application server, not by a resource adapter.
> By making this minor change to functionality (timeout configuration), fully functional JCA compliant adapter could be published directly to maven central repository. After the change projects such as https://github.com/skorhone/websphere-artemis would no longer need to be maintained



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)