1 Reply Latest reply on Aug 17, 2004 7:34 AM by Thorsten Kitz

    DestinationManager/Oracle causes some Exceptions on JBoss st

    Stefan Heckler Novice

      Hi,

      changing DestinationManager from HSQLDB to Oracle the following error occurs on startup of jboss several times (jboss 3.2.5 on SunOS 5.8). The identical configuration running on Windows 2000 runs without error:


      2004-07-05 20:34:59,926 ERROR [org.jboss.resource.connectionmanager.TxConnectionManager] There is something wrong with the pooling?
      java.lang.IllegalStateException: afterCompletion called with wrong tx! Expected: null, actual: TransactionImpl:XidImpl [FormatId=257, GlobalId=rwco_as3//57, BranchQual=]
      at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener$TxRemover.afterCompletion(TxConnectionManager.java:635)
      at org.jboss.tm.TransactionImpl.doAfterCompletion(TransactionImpl.java:1398)
      at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:406)
      at org.jboss.tm.TxManager.commit(TxManager.java:142)
      at org.jboss.mq.pm.jdbc3.PersistenceManager$TransactionManagerStrategy.endTX(PersistenceManager.java:1769)
      at org.jboss.mq.pm.jdbc3.PersistenceManager.saveToStorage(PersistenceManager.java:1020)
      at org.jboss.mq.server.MessageCache.saveToStorage(MessageCache.java:385)
      at org.jboss.mq.server.MessageReference.makeSoft(MessageReference.java:311)
      at org.jboss.mq.server.MessageCache.validateSoftReferenceDepth(MessageCache.java:332)
      at org.jboss.mq.server.MessageCache.addInternal(MessageCache.java:142)
      at org.jboss.mq.server.MessageCache.add(MessageCache.java:112)
      at org.jboss.mq.server.JMSTopic.addMessage(JMSTopic.java:351)
      at org.jboss.mq.server.JMSDestinationManager.addMessage(JMSDestinationManager.java:402)
      at org.jboss.mq.server.JMSDestinationManager.addMessage(JMSDestinationManager.java:378)
      at org.jboss.mq.server.JMSServerInterceptorSupport.addMessage(JMSServerInterceptorSupport.java:136)
      at org.jboss.mq.security.ServerSecurityInterceptor.addMessage(ServerSecurityInterceptor.java:153)
      at org.jboss.mq.server.TracingInterceptor.addMessage(TracingInterceptor.java:270)
      at org.jboss.mq.server.JMSServerInvoker.addMessage(JMSServerInvoker.java:136)
      at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:86)
      at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:356)
      at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:377)
      at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
      at java.lang.Thread.run(Thread.java:534)


      from then JMS works without error until the next startup of jboss. My queues and topics are non persistant.

      Is there a simple explanatin for this behavior?

      Stefan Heckler