[jbossts-issues] [JBoss JIRA] (JBTM-846) Allow transactional MSC and WildFly EJB container to operate with different configurations for transaction/recovery manager in a single JVM

David Lloyd (JIRA) jira-events at lists.jboss.org
Fri Jul 12 09:58:21 EDT 2013


    [ https://issues.jboss.org/browse/JBTM-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789373#comment-12789373 ] 

David Lloyd commented on JBTM-846:
----------------------------------

In regards to recovery - from a user perspective, I think that different people may be responsible/authorized for recovering transactions in the management system versus in the end-user application.  That doesn't necessarily imply two recovery managers I guess, but I think that might be an important use case to address one way or another.
                
> Allow transactional MSC and WildFly EJB container to operate with different configurations for transaction/recovery manager in a single JVM
> -------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBTM-846
>                 URL: https://issues.jboss.org/browse/JBTM-846
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: JTA, JTS, Recovery, Transaction Core, XTS
>            Reporter: Tom Jenkinson
>            Assignee: Paul Robinson
>             Fix For: 5.0.0.Final
>
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> ** This Jira is a work in progress - Paul to remove this message when description complete **
> The use case provided for this is to run a separate transaction/recovery manager for Transactional MSC to the one that WildFly is using for its (JTA/JTS) EJB container.
> This will require removal of much of the static configuration state such as StateManager references to ObjectStore

--
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


More information about the jbossts-issues mailing list