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] [Resolved] (AMQNET-416) DTC Ressource ManagerID must be confugurable
Date Wed, 15 May 2013 17:35:16 GMT

     [ https://issues.apache.org/jira/browse/AMQNET-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish resolved AMQNET-416.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 1.6.0
         Assignee: Timothy Bish  (was: Jim Gomes)

Fixed on trunk but adding optional property on the connection factory and in the connection.
 Value is set as a String to allow configuration via connection Uri.
                
> 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: Timothy Bish
>            Priority: Critical
>             Fix For: 1.6.0
>
>         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