Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

NullPointerException in MQSession class

13 views
Skip to first unread message

Henry Coe

unread,
Oct 22, 2003, 4:41:02 PM10/22/03
to
We are running an MDB in WAS 5.0.2 that works normally most of the
time, but after running for a while dies with the following exception:

[10/21/03 19:39:12:663 UTC] 350edc5 ServerSession W WMSG0031E:
Exception processing JMS Message for MDB DataLoadMdb, JMSDestination
jms/Topic/DataLoad : java.lang.NullPointerException
at com.ibm.mq.jms.MQSession.run(MQSession.java:1011)
at com.ibm.ejs.jms.JMSSessionHandle.run(JMSSessionHandle.java:922)
at com.ibm.ejs.jms.listener.ServerSession.connectionConsumerOnMessage(ServerSession.java:697)
at com.ibm.ejs.jms.listener.ServerSession.onMessage(ServerSession.java:482)
at com.ibm.ejs.jms.listener.ServerSession.dispatch(ServerSession.java:449)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ejs.jms.listener.ServerSessionDispatcher.dispatch(ServerSessionDispatcher.java:37)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:91)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:127)
at com.ibm.ejs.jms.listener.ServerSession.run(ServerSession.java:372)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)

[10/21/03 19:39:12:719 UTC] 350edc5 ExceptionUtil E CNTR0020E:
Non-application exception occurred while processing method "onMessage"
on bean "BeanId(DataLoadApp#DataLoadAppEJB.jar#DataLoadMdb, null)".
Exception data: java.lang.reflect.InvocationTargetException:
java.lang.NullPointerException
at com.ibm.mq.jms.MQSession.run(MQSession.java:1011)
at com.ibm.ejs.jms.JMSSessionHandle.run(JMSSessionHandle.java:922)
at com.ibm.ejs.jms.listener.ServerSession.connectionConsumerOnMessage(ServerSession.java:697)
at com.ibm.ejs.jms.listener.ServerSession.onMessage(ServerSession.java:482)
at com.ibm.ejs.jms.listener.ServerSession.dispatch(ServerSession.java:449)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ejs.jms.listener.ServerSessionDispatcher.dispatch(ServerSessionDispatcher.java:37)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:91)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:127)
at com.ibm.ejs.jms.listener.ServerSession.run(ServerSession.java:372)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)

I'm thinking this should be easy to diagnose if someone at IBM has the
source code to MQSession to see what is being set to null on line
1011. Anyone else encountered this problem?

0 new messages