[jboss-jira] [JBoss JIRA] (AS7-4134) Jacorb name service may not be started before Transaction Manager attempts to bind itself

[Stefan Guilhen (JIRA)]

    [ https://issues.jboss.org/browse/AS7-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675948#comment-12675948 ] 

Stefan Guilhen commented on AS7-4134:
-------------------------------------

The module dependency won't prevent services from starting in the wrong order. It looks like the transaction manager service is missing a dependency on the CORBA Naming Service. I'll look into this.
                
> Jacorb name service may not be started before Transaction Manager attempts to bind itself
> -----------------------------------------------------------------------------------------
>
>                 Key: AS7-4134
>                 URL: https://issues.jboss.org/browse/AS7-4134
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: IIOP, Transactions
>    Affects Versions: 7.1.1.Final
>            Reporter: Tom Jenkinson
>            Assignee: Stefan Guilhen
>
> When I configure the Transaction manager to use the Jacorb name service for publishing its endpoint, occasionally I get an error such as:
> 11:42:19,781 INFO  [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-1) Live Server Obtained live lock
> 11:42:20,437 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.txn.ArjunaTransactionManager: org.jboss.msc.service.StartException in service jboss.txn.ArjunaTransactionManager: JBAS010104: Start failed
> 	at org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:154)
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_18]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_18]
> 	at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_18]
> Caused by: java.lang.Exception: ARJUNA032027: Problem encountered while trying to register transaction manager with ORB!
> 	at com.arjuna.ats.jbossatx.jts.TransactionManagerService.start(TransactionManagerService.java:85)
> 	at org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:152)
> 	... 5 more
> Caused by: org.omg.CORBA.OBJECT_NOT_EXIST
> 	at org.jacorb.orb.Delegate.servant_preinvoke(Delegate.java:1859)
> 	at org.jacorb.orb.Delegate.is_a(Delegate.java:1324)
> 	at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:49) [rt.jar:1.6.0_18]
> 	at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:47) [rt.jar:1.6.0_18]
> 	at com.arjuna.orbportability.Services.registerService(Services.java:344)
> 	at com.arjuna.ats.jts.TransactionServer.registerTransactionManager(TransactionServer.java:57)
> 	at com.arjuna.ats.jbossatx.jts.TransactionManagerService.start(TransactionManagerService.java:81)
> 	... 6 more
> 11:42:20,484 INFO  [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016328: CORBA Naming Service started
> C:\hudson\workspace\blacktie-windows2003\
> As you can see, the transaction manager is trying to register itself in Jacorb before the Name service is resolvable even though the transactions module.xml has a dependency on org.omg.api.
> Perhaps it should have a different dependency?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira