5:49 a.m.
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
2:03 p.m.
New subject: [JBoss JIRA] Work started: (JBTM-784) incorrect ORB initialization
[
https://jira.jboss.org/browse/JBTM-784?page=com.atlassian.jira.plugin.sys...
]
Work on JBTM-784 started by Mark Little.
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
2:59 p.m.
New subject: [JBoss JIRA] Closed: (JBTM-784) incorrect ORB initialization
[
https://jira.jboss.org/browse/JBTM-784?page=com.atlassian.jira.plugin.sys...
]
Mark Little closed JBTM-784.
----------------------------
Resolution: Done
RecoveryORBManager now delegates ORB get/set or ORBManager, but manages its own POA.
Probably should have used inheritance back in HP days. Still could, but would be an
invasive change now. Maybe later if necessary.
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
11:12 a.m.
New subject: [JBoss JIRA] Reopened: (JBTM-784) incorrect ORB initialization
[
https://jira.jboss.org/browse/JBTM-784?page=com.atlassian.jira.plugin.sys...
]
Jonathan Halliday reopened JBTM-784:
------------------------------------
This still isn't right. ORBSetup will fail to init the OA if the ORB is already
inited, which occurs with the recovery system comes up first, as it sets the ORB but not
the OA as it has its own OA. Hence you get an "ARJUNA-22251 The ORBManager is already
associated with an ORB/OA" rather than the required OA init in ORBSetup.
ORBManager.isInitialized() probably needs to be rethought?
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
10:30 a.m.
New subject: [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
4:20 a.m.
New subject: [JBoss JIRA] Assigned: (JBTM-784) incorrect ORB initialization
[
https://jira.jboss.org/browse/JBTM-784?page=com.atlassian.jira.plugin.sys...
]
Jonathan Halliday reassigned JBTM-784:
--------------------------------------
Assignee: Jonathan Halliday (was: Mark Little)
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: Jonathan Halliday
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
4:28 a.m.
New subject: [JBoss JIRA] Closed: (JBTM-784) incorrect ORB initialization
[
https://jira.jboss.org/browse/JBTM-784?page=com.atlassian.jira.plugin.sys...
]
Jonathan Halliday closed JBTM-784.
----------------------------------
Resolution: Done
Ripped out RecoveryORBManager.
If the orb portability layer (i.e. ORBManager) has been configured by the time recovery
starts, then JacOrbRCServiceInit simply hangs the recovery OA off that existing root. In
such case the ORB addr/port are per the JacORB config file.
If the recovery system starts first, then JacOrbRCServiceInit initializes the ORBManager
and the JTSEnvironmentBean recoveryManagerPort|Address settings take effect. Thus running
RecoveryManager from the command line still works as expected.
It's not possible to have the recovery system and main ORB listening on different
sockets in the same JVM (well, classloader actually) but we can live with that - it
didn't work right before anyhow.
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: Jonathan Halliday
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
5225
days inactive
5252
days old
jbossts-issues@lists.jboss.org
6 comments
2 participants
participants (2)
-
Jonathan Halliday (JIRA) -
Mark Little (JIRA)