7 Replies Latest reply on Sep 19, 2013 5:55 PM by Tomaz Cerar

    Unable to lookup: java:/TransactionManager

    markus78 Newbie

      When I turn on DEBUG logging on my server and start it up I get the following early in the logs ( before my application has been deployed ) I'm on 7.1-Final

       

      I don't understand why org.jboss.as.naming tries to lookup the transaction manager using that JNDI name? any help appreciated.

      I'm not even sure it is a problem since my application deploys fine anyway's.

       

       

      09:08:33,077 INFO  [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA032010: JBossTS Recovery Service (tag: JBOSSTS_4_16_2_Final) - JBoss Inc.
      09:08:33,119 INFO  [com.arjuna.ats.arjuna] (MSC service thread 1-1) ARJUNA012324: Start RecoveryActivators
      09:08:33,120 DEBUG [com.arjuna.ats.arjuna] (MSC service thread 1-1) Expiry scan interval set to 43200 seconds
      09:08:33,122 DEBUG [com.arjuna.ats.arjuna] (MSC service thread 1-1) Expiry scan interval set to  43200  seconds
      09:08:33,122 DEBUG [com.arjuna.ats.arjuna] (MSC service thread 1-1) ExpiredTransactionStatusManagerScanner created, with expiry time of 43200  seconds
      09:08:33,128 DEBUG [com.arjuna.ats.arjuna] (MSC service thread 1-1) ExpiredEntryMonitor - constructed
      09:08:33,135 INFO  [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA012296: ExpiredEntryMonitor running at Wed, 22 Feb 2012 09:08:33
      09:08:33,137 DEBUG [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ExpiredTransactionStatusManagerScanner - scanning to remove items from before Tue, 21 Feb 2012 21:08:33
      09:08:33,251 DEBUG [com.arjuna.ats.arjuna] (MSC service thread 1-1) AtomicActionRecoveryModule created
      09:08:33,256 DEBUG [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor)
      09:08:33,265 DEBUG [com.arjuna.ats.txoj] (MSC service thread 1-1) TORecoveryModule created
      09:08:33,406 INFO  [com.arjuna.ats.arjuna] (MSC service thread 1-1) ARJUNA012343: RecoveryManagerImple is ready. Socket listener is turned off.
      09:08:33,406 INFO  [com.arjuna.ats.jbossatx] (MSC service thread 1-1) ARJUNA032013: Starting transaction recovery manager
      09:08:33,408 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) PeriodicRecovery: background thread Status <== SCANNING
      09:08:33,409 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) PeriodicRecovery: background thread scanning
      09:08:33,409 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) Periodic recovery first pass at Wed, 22 Feb 2012 09:08:33
      09:08:33,410 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) AtomicActionRecoveryModule first pass
      09:08:33,411 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) processing /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction transactions
      09:08:33,411 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery)
      09:08:33,411 DEBUG [com.arjuna.ats.txoj] (Periodic Recovery) TORecoveryModule - first pass
      09:08:33,414 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery)
      09:08:33,439 DEBUG [com.arjuna.ats.jta] (Periodic Recovery) Local XARecoveryModule - first pass
      09:08:33,533 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery)
      09:08:33,575 WARN  [jacorb.codeset] (MSC service thread 1-2) Warning - unknown codeset (ASCII) - defaulting to ISO-8859-1
      09:08:33,606 INFO  [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016330: CORBA ORB Service started
      09:08:33,847 INFO  [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016328: CORBA Naming Service started
      09:08:33,802 DEBUG [org.jboss.tm.TransactionManagerLocator] (MSC service thread 1-1) Unable to lookup: java:/TransactionManager: javax.naming.NameNotFoundException: Error looking up TransactionManager, service service jboss.naming.context.java.TransactionManager is not started
              at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:126) [jboss-as-naming-7.1.0.Final.jar:7.1.0.Final]
              at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74) [jboss-as-naming-7.1.0.Final.jar:7.1.0.Final]
              at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) [jboss-as-naming-7.1.0.Final.jar:7.1.0.Final]
              at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) [jboss-as-naming-7.1.0.Final.jar:7.1.0.Final]
              at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:213) [jboss-as-naming-7.1.0.Final.jar:7.1.0.Final]
              at javax.naming.InitialContext.lookup(Unknown Source) [rt.jar:1.6.0_30]
              at org.jboss.tm.TransactionManagerLocator.tryJNDI(TransactionManagerLocator.java:150) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final]
              at org.jboss.tm.TransactionManagerLocator.locate(TransactionManagerLocator.java:131) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final]
              at org.jboss.tm.TransactionManagerLocator.locateTransactionManager(TransactionManagerLocator.java:94) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final]
              at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.<init>(ServerVMClientUserTransaction.java:93) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final]
              at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.<clinit>(ServerVMClientUserTransaction.java:60) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final]
              at org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:115) [jboss-as-transactions-7.1.0.Final.jar:7.1.0.Final]
              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(Unknown Source) [rt.jar:1.6.0_30]
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_30]
              at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_30]
      
      
      09:08:33,862 DEBUG [org.jboss.tm.TransactionManagerLocator] (MSC service thread 1-1) Unable to instantiate legacy transaction manager: java.lang.ClassNotFoundException: org.jboss.tm.TxManager from [Module "org.jboss.jboss-transaction-spi:main" from local module loader @1549f94 (roots: /opt/nya/ecs-as/libexec/jboss/modules)]
              at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
              at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
              at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
              at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
              at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
              at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
              at java.lang.Class.forName0(Native Method) [rt.jar:1.6.0_30]
              at java.lang.Class.forName(Unknown Source) [rt.jar:1.6.0_30]
              at org.jboss.tm.TransactionManagerLocator.usePrivateAPI(TransactionManagerLocator.java:172) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final]
              at org.jboss.tm.TransactionManagerLocator.locate(TransactionManagerLocator.java:133) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final]
              at org.jboss.tm.TransactionManagerLocator.locateTransactionManager(TransactionManagerLocator.java:94) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final]
              at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.<init>(ServerVMClientUserTransaction.java:93) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final]
              at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.<clinit>(ServerVMClientUserTransaction.java:60) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final]
              at org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:115) [jboss-as-transactions-7.1.0.Final.jar:7.1.0.Final]
              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(Unknown Source) [rt.jar:1.6.0_30]
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_30]
              at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_30]
      
      
        • 1. Re: Unable to lookup: java:/TransactionManager
          Justin Bertram Master

          I don't think this is anything to worry about, especially since it is logged at DEBUG.  It looks like the AS7/JBossTS integration layer is searching for the transaction manager.  The bit of code used here is meant to work in multiple different versions of JBoss AS which is why it looks in a few different places (and fails).

          1 of 1 people found this helpful
          • 2. Re: Unable to lookup: java:/TransactionManager
            markus78 Newbie

            Thanks, that makes sense, and I guess I would have a lot of errors if JBoss did not actually find any transaction manager.

            • 3. Re: Unable to lookup: java:/TransactionManager
              Feng Jiang Newbie

              I found this error ,too.   I am trying to use two datasource in my application. And then  i use the bosh datasource in one method,  But i found the transaction can not rollback . Then i make the log lever at DEBUG.  I find this error ,   i think the transaction can not rollback becourse of this problem. 

              Have you solved this ? Please give me some suggestions.

              • 4. Re: Unable to lookup: java:/TransactionManager
                jaikiran pai Master

                Feng Jiang wrote:

                 

                Then i make the log lever at DEBUG.  I find this error ,   i think the transaction can not rollback becourse of this problem. 

                 

                Like already mentioned, it's not a problem/error. It's just a DEBUG message which you can ignore.

                • 5. Re: Unable to lookup: java:/TransactionManager
                  Feng Jiang Newbie

                    I failed useing multiple datasource in Seam.3.1.0.Final application , do you have some suggestions ?  Maybe  i miss some jars?

                  • 6. Re: Unable to lookup: java:/TransactionManager
                    Johnathon Lee Newbie

                    I receive a similar error [1] and note the the UserTransaction that I am getting from the JNDI lookup (org.jboss.gss.jtstest.client.Client.getUtx(Client.java:149)) fails to propagate the transaction context from the external client.

                     

                    The "Using the old JBoss transaction manager" WARN concerns me...  how high is the confidence that this is a non-issue?

                     

                     

                    [1]

                    DEBUG 19-09 16:14:13,896 (Logger.java:debug:239) main -Unable to lookup: java:/TransactionManager

                    javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:  java.naming.factory.initial

                        at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)

                        at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)

                        at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:325)

                        at javax.naming.InitialContext.lookup(InitialContext.java:392)

                        at org.jboss.tm.TransactionManagerLocator.tryJNDI(TransactionManagerLocator.java:149)

                        at org.jboss.tm.TransactionManagerLocator.locate(TransactionManagerLocator.java:130)

                        at org.jboss.tm.TransactionManagerLocator.locateTransactionManager(TransactionManagerLocator.java:93)

                        at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.<init>(ServerVMClientUserTransaction.java:93)

                        at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.<clinit>(ServerVMClientUserTransaction.java:60)

                        at org.jboss.tm.usertx.client.ClientUserTransactionObjectFactory.getUserTransaction(ClientUserTransactionObjectFactory.java:54)

                        at org.jboss.tm.usertx.client.ClientUserTransactionObjectFactory.getObjectInstance(ClientUserTransactionObjectFactory.java:77)

                        at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)

                        at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)

                        at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1496)

                        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)

                        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)

                        at javax.naming.InitialContext.lookup(InitialContext.java:392)

                        at org.jboss.gss.jtstest.client.Client.getUtx(Client.java:149)

                        at org.jboss.gss.jtstest.client.Client.startUtx(Client.java:165)

                        at org.jboss.gss.jtstest.client.Client.<init>(Client.java:61)

                        at org.jboss.gss.jtstest.client.Client.main(Client.java:44)

                    WARN  19-09 16:14:13,913 (Logger.java:warn:352) main -Using the old JBoss transaction manager null

                    • 7. Re: Unable to lookup: java:/TransactionManager
                      Tomaz Cerar Master

                      org.jnp?

                       

                      this is AS <7 client code, you will need to completely change remote client to use new APIs for AS7+