activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Marbach (JIRA)" <jira+amq...@apache.org>
Subject [jira] [Commented] (AMQNET-416) DTC Ressource ManagerID must be confugurable
Date Sun, 05 May 2013 10:42:16 GMT

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

Daniel Marbach commented on AMQNET-416:
---------------------------------------

Yes it introduces more locking overhead because the original code has some serious multi threading
issues which we discovered and fixed.
                
> DTC Ressource ManagerID must be confugurable
> --------------------------------------------
>
>                 Key: AMQNET-416
>                 URL: https://issues.apache.org/jira/browse/AMQNET-416
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ
>            Reporter: Remo Gloor
>            Assignee: Jim Gomes
>            Priority: Critical
>         Attachments: allDTCImprovments.patch, MakeResourceManagerIDConfigurable.patch
>
>
> Currently the ressource manager ID for DTC transactions is set to a value generated from
the Broker ID. With this implementation it is not possible to have more than one process connected
to the same broker because in that case an exception is thrown when the second process tries
to enlist to the transaction.
> I suggest to make this ID configurable by the application.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message