activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <jira+amq...@apache.org>
Subject [jira] [Commented] (AMQNET-416) DTC Ressource ManagerID must be confugurable
Date Sat, 04 May 2013 13:20:16 GMT

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

Timothy Bish commented on AMQNET-416:
-------------------------------------

Given the fact the patches introduce a lot of extra locking overhead into code that isn't
DTC related, and the fact that there has been a lot of changes in the code base of late I
doubt these will go in very quickly as they need review and rework in order to make them more
suitable for addition into the client. 
                
> 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