[
https://issues.jboss.org/browse/JBTM-846?page=com.atlassian.jira.plugin.s...
]
Tom Jenkinson edited comment on JBTM-846 at 7/12/13 8:31 AM:
-------------------------------------------------------------
To address Davids requirement we need to support 1xArjunaCore (for the MSC) and
1xArjunaJTA||ArjunaJTS (for the EJB container). The problem is the recovery manager, are
we expecting to launch two of those in the same VM? I presume we have to in order to
cleanly separate the MSC from the EJB container (e.g. different object stores)
was (Author: tomjenkinson):
To address Davids requirement we need to support 1xArjunaCore (for the MSC) and
1xArjunaJTA (for the EJB container). The problem is the recovery manager, are we expecting
to launch two of those in the same VM? I presume we have to in order to cleanly separate
the MSC from the EJB container (e.g. different object stores)
Allow multiple transaction managers with different configurations to
operate 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 will require removal of much of the static configuration state such as StateManager
references to ObjectStore
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 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