You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2011/03/18 21:24:29 UTC

[jira] Created: (AMQNET-321) Allow DTC Transaction to be maunally enlisted in Session

Allow DTC Transaction to be maunally enlisted in Session
--------------------------------------------------------

                 Key: AMQNET-321
                 URL: https://issues.apache.org/jira/browse/AMQNET-321
             Project: ActiveMQ .Net
          Issue Type: Improvement
          Components: ActiveMQ
    Affects Versions: 1.5.0
            Reporter: Timothy Bish
            Assignee: Timothy Bish
            Priority: Minor
             Fix For: 1.5.1, 1.6.0


Currently the .NET transaction support is limited to synchronous consumers since it relies on there being an Ambient transaction in order to automatically enlist in a distributed transaction.  When an asynchronous listener is registered it dispatches in a separate thread which can't see the Ambient TX in the main thread.  To allow for async listeners to participate the Session needs to allow the client app to force an enlistment in a TX, either by forcing the Ambient transaction of a TransactionScope or by using CommitableTransaction objects.  This is a bit more onerous on the client since they need to more carefully manage TX state but for those that really want it we should go ahead and allow it.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (AMQNET-321) Allow DTC Transaction to be maunally enlisted in Session

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQNET-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQNET-321.
---------------------------------

    Resolution: Fixed

fixed in trunk and the 1.5.x branch

> Allow DTC Transaction to be maunally enlisted in Session
> --------------------------------------------------------
>
>                 Key: AMQNET-321
>                 URL: https://issues.apache.org/jira/browse/AMQNET-321
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>          Components: ActiveMQ
>    Affects Versions: 1.5.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 1.5.1, 1.6.0
>
>
> Currently the .NET transaction support is limited to synchronous consumers since it relies on there being an Ambient transaction in order to automatically enlist in a distributed transaction.  When an asynchronous listener is registered it dispatches in a separate thread which can't see the Ambient TX in the main thread.  To allow for async listeners to participate the Session needs to allow the client app to force an enlistment in a TX, either by forcing the Ambient transaction of a TransactionScope or by using CommitableTransaction objects.  This is a bit more onerous on the client since they need to more carefully manage TX state but for those that really want it we should go ahead and allow it.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira