[jbossts-issues] [JBoss JIRA] Updated: (JBTM-591) Default configuration for com.arjuna.ats.arjuna.coordinator.transactionStatusManagerEnable should be DISABLED.

[Vicky Kak (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBTM-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vicky Kak updated JBTM-591:
---------------------------

    Description: 
In a typical JEE environment the RecoveryManager and TransactionManager are usually running in the same JVM, it is common use case. And for such usecases the interaction between the TM and RM should not use sockets and thus the listeners on the TransactionStatusManager are not required. Disabling the com.arjuna.ats.arjuna.coordinator.transactionStatusManagerEnable property as default setting would make sense.


  was:
In typical JEE environment the RecoveryManager and TransactionManager are usually running in the same JVM, it is common use case. And for such usecases the interaction between the TM and RM should not use sockets and thus the listeners on the TransactionStatusManager are not required. Disabling the com.arjuna.ats.arjuna.coordinator.transactionStatusManagerEnable property as default setting would make sense.




> Default configuration for com.arjuna.ats.arjuna.coordinator.transactionStatusManagerEnable should be DISABLED.
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: JBTM-591
>                 URL: https://jira.jboss.org/jira/browse/JBTM-591
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Configuration
>            Reporter: Vicky Kak
>            Assignee: Vicky Kak
>
> In a typical JEE environment the RecoveryManager and TransactionManager are usually running in the same JVM, it is common use case. And for such usecases the interaction between the TM and RM should not use sockets and thus the listeners on the TransactionStatusManager are not required. Disabling the com.arjuna.ats.arjuna.coordinator.transactionStatusManagerEnable property as default setting would make sense.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira