1 Reply Latest reply on Mar 4, 2004 3:56 AM by normann

    Timeout in JBoss Autonumber EJB

    normann

      I've created a J2EE application and it ran perfectly (with a few deadlocks now and then) in JBoss 3.0.8. After upgrading to JBoss 3.2.3, the server runs perfectly for some time, maybe a day, then suddenly everything locks up and timeouts starts to occur, always starting with this exception stacktrace below.

      Do anyone have any experiences with the built-in autonumber and timeouts? What should I do about it?

      20:08:05,670 WARN [TransactionImpl] Transaction TransactionImpl:XidImpl [FormatId=257, GlobalId=b-one//309565, BranchQual=] timed out. status=STATUS_ACTIVE
      20:08:05,671 ERROR [BeanLock] PoolThread-38Saw rolled back tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=b-one//309565, BranchQual=] waiting for txLock
      20:08:05,671 ERROR [LogInterceptor] TransactionRolledbackException in method: public abstract java.lang.Integer org.jboss.varia.autonumber.AutoNumber.getValue
      () throws java.rmi.RemoteException, causedBy:
      java.lang.RuntimeException: Transaction marked for rollback, possibly a timeout
      at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.waitForTx(QueuedPessimisticEJBLock.java:366)
      at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.doSchedule(QueuedPessimisticEJBLock.java:236)
      at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.schedule(QueuedPessimisticEJBLock.java:183)
      at org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor.java:85)
      at org.jboss.ejb.plugins.EntityCreationInterceptor.invoke(EntityCreationInterceptor.java:54)
      at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:84)
      at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:267)
      at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:128)
      at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:118)
      at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191)
      at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
      at org.jboss.ejb.EntityContainer.internalInvoke(EntityContainer.java:489)
      at org.jboss.ejb.Container.invoke(Container.java:700)
      at sun.reflect.GeneratedMethodAccessor37.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
      at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:101)
      at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:90)
      at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
      at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:45)
      at org.jboss.proxy.ejb.EntityInterceptor.invoke(EntityInterceptor.java:97)
      at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:85)
      at $Proxy30.getValue(Unknown Source)
      at org.jboss.varia.autonumber.AutoNumberFactory.getNextInteger(AutoNumberFactory.java:91)

      [snip]

        • 1. Re: Timeout in JBoss Autonumber EJB
          normann

          This problem seems to be related to the pg74.1jdbc3.jar Postgres 7.4 DB JDBC Driver we used to connect to a 7.2 server. After running for some time, we experienced the time-outs specified earlier. We have downgraded our driver to pg73jdbc3.jar and everything runs smoothly.