0 Replies Latest reply on Apr 25, 2003 10:12 AM by Bill

    Jboss deadlock when used with Tomcat virtual hosts

    Bill Newbie


      When using Tomcat 3.2.3, each virtual host creates its own JVM (which is not configurable in 3.2.3 -- I don't know about 4.0). Whenever a user access the same EJB or requests a JDBC connection from the pool when a second user attempts to access the same data at the same time, a deadlock condition occurs and Jboss will no longer be able to obtain database access (Postgres in our case) or something related. When two users access the same data from the same virtual host, there are no problems.

      Has anyone had this problem before? My configuration and error log is shown below. Any help is greatly appreciated.

      Jboss version is 2.4.4 and Tomcat version is 3.2.3. Tomcat is integrated in Jboss.

      My Tomcat server.xml files is configured as follows:












      Here is the log after the deadlock occurs and then times out:
      [INFO ] [Thread-122] :2003-04-24 18:22:51,502:com.im.ejb.HomeInterfaceFactory:Look up complete for interface com.im.ejb.Attendee

      [INFO ] [Thread-122] :2003-04-24 18:22:51,504:org.jboss.jdbc.XADataSourceLoader.PostgresDB:Resource
      'org.jboss.pool.jdbc.xa.wrapper.XAResourceImpl@39defe' enlisted for 'org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@4030c4'.

      [INFO ] [Thread-122] :2003-04-24 18:22:51,746:org.jboss.jdbc.XADataSourceLoader.PostgresDB:Resource 'org.jboss.pool.jdbc.xa.wrapper.XAResourceImpl@39defe' enlisted for 'org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@4030c4'.

      [WARN ] [Thread-140] :2003-04-24 19:11:17,157:org.jboss.tm.TxCapsule:Transaction XidImpl [FormatId=257, GlobalId=michael//584, BranchQual=] timed out. status=STATUS_ACTIVE

      [WARN ] [Thread-141] :2003-04-24 19:11:35,012:org.jboss.tm.TxCapsule:Transaction XidImpl [FormatId=257, GlobalId=michael//588, BranchQual=] timed out. status=STATUS_ACTIVE