[jira] [Commented] (AMQNET-416) DTC Ressource ManagerID must be confugurable
[ https://issues.apache.org/jira/browse/AMQNET-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659907#comment-13659907 ] Daniel Marbach commented on AMQNET-416: --- Nice!. Thanks a lot! > 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
[jira] [Commented] (AMQNET-416) DTC Ressource ManagerID must be confugurable
[ 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
[jira] [Commented] (AMQNET-416) DTC Ressource ManagerID must be confugurable
[ 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
[jira] [Commented] (AMQNET-416) DTC Ressource ManagerID must be confugurable
[ https://issues.apache.org/jira/browse/AMQNET-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649066#comment-13649066 ] Daniel Marbach commented on AMQNET-416: --- Just to make sure: We have now the DTC fixes running in test, staging and even production environment and it runs perfectly fine. Can we proceed and do the necessary changes. @Timothy patches of patches are welcome :p > 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
[jira] [Commented] (AMQNET-416) DTC Ressource ManagerID must be confugurable
[ https://issues.apache.org/jira/browse/AMQNET-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647065#comment-13647065 ] Timothy Bish commented on AMQNET-416: - Might be more usable if the ResourceManagerId GUID can be configured on the NetTxConnectionFactory such that it can be set via a Uri property as well as set on the NetTxConnection itself. Also why is it static? And all the NetTx code needs to be .NET 2.0 compatible. > 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
[jira] [Commented] (AMQNET-416) DTC Ressource ManagerID must be confugurable
[ https://issues.apache.org/jira/browse/AMQNET-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615398#comment-13615398 ] Remo Gloor commented on AMQNET-416: --- Each servce or in case of out scaling each instance of the service must have an unique id. The id must be consistent between restarts. > 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
[jira] [Commented] (AMQNET-416) DTC Ressource ManagerID must be confugurable
[ 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
