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

Jonathan Halliday (JIRA) jira-events at lists.jboss.org
Mon Sep 13 12:12:12 EDT 2010

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

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


More information about the jbossts-issues mailing list