activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kate Macdonald (JIRA)" <jira+amq...@apache.org>
Subject [jira] [Commented] (AMQNET-416) DTC Ressource ManagerID must be confugurable
Date Wed, 27 Mar 2013 15:23:16 GMT

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

Kate Macdonald commented on AMQNET-416:
---------------------------------------

Thanks for the patch. 

Could you clarify what conditions the configured value should meet? Should it be consistent
between service restarts, for example?
                
> 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