Hello!
Upon changing the JMS-JDBC-persistence-manager from Oracle 8.1.7 to Oracle 9.2.0.1 the following exception is thrown after running 20 hours successfully:
2004-03-18 15:18:17,331 WARN ...
at java.lang.Thread.run(Thread.java:536)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:655)
at
org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:177)
at org.jboss.mq.SpySession.run(SpySession.java:293)
at
org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:415)
at
org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:601)
at
org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:322)
at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:376)
javax.transaction.RollbackException: Unable to commit,
tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=www4//1281, BranchQual=]
status=STATUS_NO_TRANSACTION
2004-03-18 15:18:17,203 ERROR [org.jboss.jms.asf.StdServerSession] failed
to commit/rollback
at java.lang.Thread.run(Thread.java:536)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:655)
at
org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:177)
at org.jboss.mq.SpySession.run(SpySession.java:293)
at
org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:415)
at
org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:601)
at
org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:322)
at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:355)
at
org.jboss.tm.TransactionImpl.prepareResources(TransactionImpl.java:1340)
at org.jboss.mq.SpyXAResource.prepare(SpyXAResource.java:178)
javax.transaction.xa.XAException
2004-03-18 15:18:17,172 WARN [org.jboss.tm.TransactionImpl] XAException:
tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=www4/
/1281, BranchQual=] errorCode=XAER_RMERR
We are using JBoss 3.2.0RC1 and Oracle 9.2.0.1 (as JMS-JDBC-persistence-manager and backend for EJBs) with Tx connections.
What can be the reason for this exception?
Kind regards,
Bernhard
