1 2 Previous Next 18 Replies Latest reply on Aug 7, 2006 3:34 PM by Armen

    TransactionManager Name not bound?

    Saroj Kachhwal Newbie

      Hi Everybody!
      I am trying to use TransactionManager for Jboss Cahe (v 4.0.2)
      My code is as follws:
      ===================================================
      objTreeCache = new TreeCache();
      objPropertyConfigurator = new PropertyConfigurator(); objPropertyConfigurator.configure(objTreeCache,"treecache-service.xml");
      String strTransactionMgrLookup = objTreeCache.getTransactionManagerLookupClass();
      TransactionManagerLookup objTransactionManagerLookup (TransactionManagerLookup)Class.forName(strTransactionMgrLookup).newInstance();
      TransactionManager objTransactionManager = objTransactionManagerLookup.getTransactionManager();
      ===================================================
      I am using Jboss All configuration.
      I dont know why I am getting the following error:
      javax.naming.NameNotFoundException: TransactionManager not bound

      However Jndi view in jxm console is showing the "TransactionManager" name bound in the namespace.
      Can someone please help me to resolve this issue.
      Thanks in advance.
      Saroj

        • 1. Re: TransactionManager Name not bound?
          Manik Surtani Master

          Try the following to get a hold of the tx manager.

          objTreeCache = new TreeCache();
          objPropertyConfigurator = new PropertyConfigurator(); objPropertyConfigurator.configure(objTreeCache,"treecache-service.xml");
          
          
          TransactionManager mgr = objTreeCache.getTransactionManager();
          


          Which tx manager have you specified in treecache-service.xml?


          • 2. Re: TransactionManager Name not bound?
            Saroj Kachhwal Newbie

            I have configures xml file as follows:
            ==============================

            jboss:service=Naming
            jboss:service=TransactionManager
            org.jboss.cache.JBossTransactionManagerLookup
            ==================================
            How to configure TxMamanger?
            Is there any attribute through which we can set Transactrion manager in the xml file?
            I want to use JBoss TransactionManager which this lookup class is returning through jndi name : "java:/TransactionManager"
            Thanks and regards
            Saroj

            • 3. Re: TransactionManager Name not bound?
              Saroj Kachhwal Newbie

              Sorry for incorret paste of xml file content. The correct content is as follow:
              ==================================


              jboss:service=Naming
              jboss:service=TransactionManager
              org.jboss.cache.JBossTransactionManagerLookup
              ====================================
              Looking forward for your reply.
              Thanks
              Saroj

              • 4. Re: TransactionManager Name not bound?
                Ben Wang Master

                Besides your own code, when you start JBoss AS, did you see any error complaining the same thing about JBossManager not found?

                • 5. Re: TransactionManager Name not bound?
                  Saroj Kachhwal Newbie

                  No, I am running my application as standalone, i.e. not inside jboss as ear/war. But I start jboss before running my application as it uses jndi service.
                  Am I doing wrong something?
                  Thanks
                  Saroj

                  • 6. Re: TransactionManager Name not bound?
                    Ben Wang Master

                    To use JBossTransactionManager, you will have to run JBossCache inside JBossAS. You can only access UserTransaction via jndi.

                    • 7. Re: TransactionManager Name not bound?
                      Alex Levine Newbie

                      I get a similar "TransactionMananger not bound" error, however it occurrs in my JBoss AS startup. I am running jboss-4.0.4.GA with the ejb3-clustered configuration. I have not changed any of the config files from the defaults and I get the following exception trace in server.log when I start up the AS:


                      2006-05-10 09:42:00,443 DEBUG [org.jboss.cache.TreeCache] Creating jboss.cache:service=EJB3EntityTreeCache
                      2006-05-10 09:42:00,451 DEBUG [org.jboss.cache.TreeCache] failed looking up TransactionManager, will not use transactions
                      javax.naming.NameNotFoundException: TransactionManager not bound
                      at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
                      at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
                      at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
                      at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
                      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
                      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
                      at javax.naming.InitialContext.lookup(InitialContext.java:351)
                      at org.jboss.cache.JBossTransactionManagerLookup.getTransactionManager(JBossTransactionManagerLookup.java:18)
                      at org.jboss.cache.TreeCache._createService(TreeCache.java:1187)
                      at org.jboss.cache.TreeCache.createService(TreeCache.java:1175)
                      at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
                      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
                      at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
                      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                      at java.lang.reflect.Method.invoke(Method.java:585)
                      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
                      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
                      at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
                      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260)
                      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
                      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
                      at $Proxy0.create(Unknown Source)
                      at org.jboss.system.ServiceController.create(ServiceController.java:330)
                      at org.jboss.system.ServiceController.create(ServiceController.java:273)
                      at org.jboss.system.ServiceController.create(ServiceController.java:349)
                      at org.jboss.system.ServiceController.create(ServiceController.java:273)
                      at org.jboss.system.ServiceController.create(ServiceController.java:349)
                      at org.jboss.system.ServiceController.create(ServiceController.java:273)
                      at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
                      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                      at java.lang.reflect.Method.invoke(Method.java:585)
                      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
                      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
                      at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
                      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260)
                      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
                      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:190)
                      at $Proxy4.create(Unknown Source)
                      at org.jboss.deployment.SARDeployer.create(SARDeployer.java:258)
                      at org.jboss.deployment.MainDeployer.create(MainDeployer.java:953)
                      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807)
                      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
                      at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
                      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                      at java.lang.reflect.Method.invoke(Method.java:585)
                      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
                      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
                      at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
                      at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
                      at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
                      at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
                      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260)
                      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
                      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:190)
                      at $Proxy6.deploy(Unknown Source)
                      at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:334)
                      at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:522)
                      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:207)
                      at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:280)
                      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
                      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
                      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                      at java.lang.reflect.Method.invoke(Method.java:585)
                      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
                      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
                      at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
                      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260)
                      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
                      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
                      at $Proxy0.start(Unknown Source)
                      at org.jboss.system.ServiceController.start(ServiceController.java:417)
                      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                      at java.lang.reflect.Method.invoke(Method.java:585)
                      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
                      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
                      at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
                      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260)
                      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
                      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:190)
                      at $Proxy4.start(Unknown Source)
                      at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
                      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
                      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
                      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
                      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755)
                      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                      at java.lang.reflect.Method.invoke(Method.java:585)
                      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
                      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
                      at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
                      at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
                      at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
                      at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
                      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:260)
                      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
                      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:190)
                      at $Proxy5.deploy(Unknown Source)
                      at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
                      at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
                      at org.jboss.Main.boot(Main.java:200)
                      at org.jboss.Main$1.run(Main.java:464)
                      at java.lang.Thread.run(Thread.java:595)


                      Any suggestions on how to remedy this issue??

                      • 8. Re: TransactionManager Name not bound?
                        Brian Stansberry Master

                        Does your deploy/ejb3-entity-cache-service.xml file look like this at the beginning?

                        <mbean code="org.jboss.cache.TreeCache" name="jboss.cache:service=EJB3EntityTreeCache">
                         <depends>jboss:service=Naming</depends>
                         <depends>jboss:service=TransactionManager</depends>
                        
                         <!-- Configure the TransactionManager -->
                         <attribute name="TransactionManagerLookupClass">org.jboss.cache.JBossTransactionManagerLookup</attribute>
                        


                        • 9. Re: TransactionManager Name not bound?
                          Alex Levine Newbie

                          yes. exactly like that.

                          -Alex

                          • 10. Re: TransactionManager Name not bound?
                            Bret Patterson Newbie

                             

                            "ablevine1" wrote:
                            yes. exactly like that.

                            -Alex


                            Did you ever find a solution for this? I'm having the same problem.

                            • 11. Re: TransactionManager Name not bound?
                              Alex Levine Newbie

                              no. not yet, as no one has responded

                              • 12. Re: TransactionManager Name not bound?
                                Armen Newbie

                                I am seeing the same thing on all environments (Windows and Linux). I am seeing this on fresh installations, performed with the following command:

                                java -jar jboss-4.0.4.GA-Patch1-installer.jar -installGroup ejb3-cluster

                                I have made no modifications or deployed any applications.

                                I am using JDK 1.5.0_06.

                                • 13. Re: TransactionManager Name not bound?
                                  Simeon Koptelov Newbie

                                  Encountered last problem too. Solved with adding the following to cache MBean XML:

                                  jboss:service=ClientUserTransaction

                                  • 14. Re: TransactionManager Name not bound?
                                    Armen Newbie

                                     

                                    "skoptelov" wrote:
                                    adding the following to cache MBean XML


                                    Hi, sorry, which file exactly, and what section?

                                    1 2 Previous Next