[jbossts-issues] [JBoss JIRA] Commented: (JBTM-784) incorrect ORB initialization
[
https://jira.jboss.org/browse/JBTM-784?page=com.atlassian.jira.plugin.sys...
]
Jonathan Halliday commented on JBTM-784:
----------------------------------------
After further thought I'm leaning towards simply killing off RecoveryORBManager. At
first I thought it needed to be kept because its OA was one with the Policies for
recovery, but that's not the case. The Policy[] is actually on a child OA handled by
JacOrbRCServiceInit, not the root one held by the RecoveryORBManager. Unless someone can
give me a convincing use case for using a different base OA for the main system vs.
recovery system, it's going to be best to remove RecoveryORBManager and just use
ORBManager throughout.
incorrect ORB initialization
----------------------------
Key: JBTM-784
URL: https://jira.jboss.org/browse/JBTM-784
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JTS, Recovery
Affects Versions: 4.12.0
Reporter: Jonathan Halliday
Assignee: Mark Little
Fix For: 4.13.0
When running the TransactionManager and RecoveryManager in the same JVM, the ORB
initialization incorrectly attempts to setup the ORB twice:
WARN: ARJUNA-22251 The ORBManager is already associated with an ORB/OA.
The correct model is one ORB and two POAs, whereas we currently have two ORBs. See
ORBManager; RecoveryORBManager (both have ORB field); ORB/InternalORB (why the subclass?)
method initORB->InitLoader->ORBSetup; JacOrbRCServiceInit
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira