[jbossts-issues] [JBoss JIRA] Closed: (JBTM-784) incorrect ORB initialization

Jonathan Halliday (JIRA) jira-events at lists.jboss.org
Wed Sep 22 05:28:28 EDT 2010


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

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

        


More information about the jbossts-issues mailing list