StdServerSessionFailed NullpointerException

[bpeeters]

I've a Jboss 3.2.2 server running with a mysql DB (version4) server to persist the JMS messages.
It runs on Redhat 9
Somethimes this exception occurs:


2004-03-11 14:06:30,563 ERROR [org.jboss.jms.asf.StdServerSession] failed to commit/rollback
org.jboss.mq.SpyXAException: - nested throwable: (org.jboss.mq.SpyJMSException: Cannot process a transaction; - nested throwable: (java.lang.NullPointerException))
at org.jboss.mq.SpyXAResource.commit(SpyXAResource.java:105)
at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:307)
at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:633)
at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:433)
at org.jboss.mq.SpySession.run(SpySession.java:298)
at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:180)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:727)
at java.lang.Thread.run(Thread.java:534)
Caused by: org.jboss.mq.SpyJMSException: Cannot process a transaction; - nested throwable: (java.lang.NullPointerException)
at org.jboss.mq.Connection.send(Connection.java:932)
at org.jboss.mq.SpyXAResourceManager.commit(SpyXAResourceManager.java:127)
at org.jboss.mq.SpyXAResource.commit(SpyXAResource.java:103)
... 7 more
Caused by: java.lang.NullPointerException
at org.jboss.mq.pm.TxManager.releaseList(TxManager.java:234)
at org.jboss.mq.pm.TxManager.rollbackTx(TxManager.java:150)
at org.jboss.mq.server.JMSDestinationManager.transact(JMSDestinationManager.java:451)
at org.jboss.mq.server.JMSServerInterceptorSupport.transact(JMSServerInterceptorSupport.java:186)
at org.jboss.mq.server.TracingInterceptor.transact(TracingInterceptor.java:438)
at org.jboss.mq.server.JMSServerInvoker.transact(JMSServerInvoker.java:186)
at org.jboss.mq.il.jvm.JVMServerIL.transact(JVMServerIL.java:328)
at org.jboss.mq.Connection.send(Connection.java:928)
... 9 more
2004-03-11 14:06:30,565 ERROR [org.jboss.jms.asf.StdServerSession] failed to commit/rollback
org.jboss.mq.SpyXAException: - nested throwable: (org.jboss.mq.SpyJMSException: Cannot process a transaction; - nested throwable: (java.lang.NullPointerException))
at org.jboss.mq.SpyXAResource.commit(SpyXAResource.java:105)
at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:307)
at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:633)
at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:433)
at org.jboss.mq.SpySession.run(SpySession.java:298)
at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:180)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:727)
at java.lang.Thread.run(Thread.java:534)
Caused by: org.jboss.mq.SpyJMSException: Cannot process a transaction; - nested throwable: (java.lang.NullPointerException)
at org.jboss.mq.Connection.send(Connection.java:932)
at org.jboss.mq.SpyXAResourceManager.commit(SpyXAResourceManager.java:127)
at org.jboss.mq.SpyXAResource.commit(SpyXAResource.java:103)
... 7 more
Caused by: java.lang.NullPointerException
at org.jboss.mq.pm.TxManager.releaseList(TxManager.java:234)
at org.jboss.mq.pm.TxManager.rollbackTx(TxManager.java:150)
at org.jboss.mq.server.JMSDestinationManager.transact(JMSDestinationManager.java:451)
at org.jboss.mq.server.JMSServerInterceptorSupport.transact(JMSServerInterceptorSupport.java:186)
at org.jboss.mq.server.TracingInterceptor.transact(TracingInterceptor.java:438)
at org.jboss.mq.server.JMSServerInvoker.transact(JMSServerInvoker.java:186)
at org.jboss.mq.il.jvm.JVMServerIL.transact(JVMServerIL.java:328)
at org.jboss.mq.Connection.send(Connection.java:928)

[adrian.brock]

I have never seen that problem before, but I can tell you that code doesn't
exist anymore in the latest codebase.

Looks to me like the transaction has already been rolled back? You will need to
post more of your log to see what is going on.
Try enabling TRACE logging for org.jboss.mq

Since you are using Redhat 9 make sure you have
export LD_ASSUME_KERNEL=2.4.1
to disable their buggy nptl backport

Regards,
Adrian

[bartvh]

From what version on is that code gone? Is there a released version?

I really need a fix here. At first, the problem did not seem to do too much harm, but lately--probably because the server is used more--it sometimes renders the jms server totally useless : all (OIL) connections fail with a connection refused.

Is there any way to isolate the problem a bit more? If I try to set TRACE level debugging on for the whole jboss.mq, I get way too much output.

Bart.

[genman]

The FAQ recommends using UIL2 connection factory. (This may not be related to your issue, but should prevent deadlocks, etc.)