[JBoss JIRA] Created: (JBTM-416) When running in a server the Recovery Manager does not reuse the servers' orb
11:41 a.m.
When running in a server the Recovery Manager does not reuse the servers' orb
-----------------------------------------------------------------------------
Key: JBTM-416
URL: https://jira.jboss.org/jira/browse/JBTM-416
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Application Server Integration
Affects Versions: 4.4.0.GA
Reporter: Michael Musgrove
Assignee: Jonathan Halliday
Fix For: 4.4.0.GA
Start two servers on the same host but bound to different interfaces. The Recovery manager
on the second server fails to start since it tries to create a new ORB on the default
jacorb address (see JacOrbRCServiceInit.java) - ie it neither reuses the existing server
orb nor does it bind to the jboss.bind.address.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:57 a.m.
New subject: [JBoss JIRA] Updated: (JBTM-416) When running in a server the Recovery Manager does not reuse the servers' orb
[
https://jira.jboss.org/jira/browse/JBTM-416?page=com.atlassian.jira.plugi...
]
Jonathan Halliday updated JBTM-416:
-----------------------------------
Fix Version/s: 4.6
(was: 4.4.0.GA)
When running in a server the Recovery Manager does not reuse the
servers' orb
-----------------------------------------------------------------------------
Key: JBTM-416
URL: https://jira.jboss.org/jira/browse/JBTM-416
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Application Server Integration
Affects Versions: 4.4.0.GA
Reporter: Michael Musgrove
Assignee: Jonathan Halliday
Fix For: 4.6
Start two servers on the same host but bound to different interfaces. The Recovery
manager on the second server fails to start since it tries to create a new ORB on the
default jacorb address (see JacOrbRCServiceInit.java) - ie it neither reuses the existing
server orb nor does it bind to the jboss.bind.address.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:49 a.m.
New subject: [JBoss JIRA] Commented: (JBTM-416) When running in a server the Recovery Manager does not reuse the servers' orb
[
https://jira.jboss.org/jira/browse/JBTM-416?page=com.atlassian.jira.plugi...
]
Jonathan Halliday commented on JBTM-416:
----------------------------------------
Hmm, this seems to have been inadvertently fixed as a result of changes for another issue.
The bootstrap when running inside JBossAS is now
ORB orb = ORB.getInstance("jboss-atx");
org.omg.PortableServer.POA rootPOA =
org.omg.PortableServer.POAHelper.narrow(theCorbaORB.resolve_initial_references("RootPOA"));
orb.setOrb(theCorbaORB);
OA oa = OA.getRootOA(orb);
oa.setPOA(rootPOA);
RecoveryORBManager.setORB(orb);
RecoveryORBManager.setPOA(oa);
Which leads to the recovery system sharing the same ORB and hence same addr+port as the
regular transaction manager. Since that addr+port is correctly configured, the servers
avoid each other:
[jhalli@rollback ~]$ lsof | grep TCP | grep java | grep 47
java 9859 jhalli 47u IPv4 140737 0t0 TCP
localhost.localdomain:4713 (LISTEN)
java 9859 jhalli 50u IPv4 140745 0t0 TCP
localhost.localdomain:4712 (LISTEN)
java 10151 jhalli 47u IPv4 141011 0t0 TCP
rollback.the-transcend.com:4713 (LISTEN)
java 10151 jhalli 50u IPv4 141019 0t0 TCP
rollback.the-transcend.com:4712 (LISTEN)
Hopefully sharing an orb configuration is ok, I guess we won't know for sure until we
start crash recovery testing JTS embedded in JBossAS.
When running in a server the Recovery Manager does not reuse the
servers' orb
-----------------------------------------------------------------------------
Key: JBTM-416
URL: https://jira.jboss.org/jira/browse/JBTM-416
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Application Server Integration
Affects Versions: 4.4.0.GA
Reporter: Michael Musgrove
Assignee: Jonathan Halliday
Fix For: 4.6
Start two servers on the same host but bound to different interfaces. The Recovery
manager on the second server fails to start since it tries to create a new ORB on the
default jacorb address (see JacOrbRCServiceInit.java) - ie it neither reuses the existing
server orb nor does it bind to the jboss.bind.address.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:44 p.m.
New subject: [JBoss JIRA] Closed: (JBTM-416) When running in a server the Recovery Manager does not reuse the servers' orb
[
https://jira.jboss.org/jira/browse/JBTM-416?page=com.atlassian.jira.plugi...
]
Jonathan Halliday closed JBTM-416.
----------------------------------
Resolution: Done
When running in a server the Recovery Manager does not reuse the
servers' orb
-----------------------------------------------------------------------------
Key: JBTM-416
URL: https://jira.jboss.org/jira/browse/JBTM-416
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Application Server Integration
Affects Versions: 4.4.0.GA
Reporter: Michael Musgrove
Assignee: Jonathan Halliday
Fix For: 4.6
Start two servers on the same host but bound to different interfaces. The Recovery
manager on the second server fails to start since it tries to create a new ORB on the
default jacorb address (see JacOrbRCServiceInit.java) - ie it neither reuses the existing
server orb nor does it bind to the jboss.bind.address.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5690
days inactive
5834
days old
jbossts-issues@lists.jboss.org
3 comments
2 participants
participants (2)
-
Jonathan Halliday (JIRA) -
Michael Musgrove (JIRA)