2 Replies Latest reply on Feb 27, 2006 7:38 PM by Luis Daniel Rangel Tovar

    TransactionManager not bound

    Luis Daniel Rangel Tovar Newbie

      Fresh jBoss 4.0.4RC1 installation, on early bootup log I found the following:

      ===============================================================================
      . JBoss Bootstrap Environment
      . JBOSS_HOME: D:\Java\jBoss-4.0.4RC1\bin\\..
      . JAVA: D:\Java\JDK1.5.0_06\bin\java
      . JAVA_OPTS: -server -Xms128m -Xmx128m
      . CLASSPATH: D:\Java\JDK1.5.0_06\lib\tools.jar;D:\Java\jBoss-4.0.4RC1\bin\\run.jar
      ==============================================================================
      19:41:41,500 INFO [Server] Starting JBoss (MX MicroKernel)...
      19:41:41,515 INFO [Server] Release ID: JBoss [Zion] 4.0.4RC1 (build: CVSTag=JBoss_4_0_4_RC1 date=200602071519)
      19:41:41,531 INFO [Server] Home Dir: D:\Java\jBoss-4.0.4RC1
      19:41:41,531 INFO [Server] Home URL: file:/D:/Java/jBoss-4.0.4RC1/
      19:41:41,531 INFO [Server] Patch URL: null
      19:41:41,531 INFO [Server] Server Name: default
      19:41:41,531 INFO [Server] Server Home Dir: D:\Java\jBoss-4.0.4RC1\server\default
      19:41:41,531 INFO [Server] Server Home URL: file:/D:/Java/jBoss-4.0.4RC1/server/default/
      19:41:41,531 INFO [Server] Server Temp Dir: D:\Java\jBoss-4.0.4RC1\server\default\tmp
      19:41:41,531 INFO [Server] Root Deployment Filename: jboss-service.xml
      19:41:42,875 INFO [ServerInfo] Java version: 1.5.0_06,Sun Microsystems Inc.
      19:41:42,875 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_06-b05,Sun Microsystems Inc.
      19:41:42,875 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
      19:41:45,468 INFO [Server] Core system initialized
      19:41:50,640 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
      19:41:58,765 INFO [SocketServerInvoker] Invoker started for locator: InvokerLocator [socket://148.202.167.109:3873/]
      19:42:01,343 INFO [AspectDeployer] Deployed AOP: file:/D:/Java/jBoss-4.0.4RC1/server/default/deploy/ejb3-interceptors-aop.xml
      19:42:26,265 INFO [WebService] Using RMI server codebase: http://DS-SW-0001:8083/
      19:42:26,828 WARN [EJBTimerServiceImpl] Cannot obtain TransactionManager from JNDI, using TxManager.getInstance(): javax.naming.NameNotFoundException: TransactionManager not bound
      ...
      ...
      ...
      


      ... then, EntitiManager transactions have lots of issues, TransactionInterceptor fails, i have to manage all transactions programatically, while I want them to be ContainerManaged. Since it's on early bootup stage, I believe it's a configuration thing on wich I'm lost.

      Funny thing, if I search Naming using a JNDI Browser when the boot is complete I can see

      TransactionManager (org.jboss.tm.TxManager)
      TransactionPropagationContextExporter(org.jboss.tm.TransactionPropagationContextFactory)
      TransactionPropagationContextImporter(org.jboss.tm.TransactionPropagationContextImporter)
      XAConnectionFactory(org.jboss.mq.SpyXAConnectionFactory)
      


      ... however, Container Managed Transaction just won't work.

      I use them by just fetching an EntityManager from Naming, or even an EntityManagerFactory.createEntityManager or EntityManagerFactory.getEntityManager, they all fail CMT.

      Am I doing something wrong ?
      Is there a workaround ?

      Thanks in advance.

      I really don't want to hadle transactions, they shuld be ContainerManaged, thats the idea when using those abstract layers.


      jBoss 4.0.4RC1
      PostgreSQL 8.0
      DebianGNU Linux Xeon Dual / WinXP P4
      EJB3
      Hibernate3.1.2