RE: Error in JMSServer when trying to process XML Data.

It means your implementation of MessageListener.onMessage() is throwing a
NullPointerException.
Ideally, this would be logged on the client side - and will be in the next
alpha release.
 
-Tim
 


  _____  

From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
[mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of Praveen
Upadhyay
Sent: Thursday, 10 November 2005 11:28 PM
To: [email protected]
Subject: [openjms-user] Error in JMSServer when trying to process XML Data.


 
   I am facing a error when I am trying to process the XML data. The Error
is:
 
       17:48:13.656 ERROR [Scheduler-Worker-12] - java.rmi.RemoteException:
null; nested exception is: 
 java.lang.NullPointerException
java.rmi.RemoteException: null; nested exception is: 
 java.lang.NullPointerException 
 at
org.exolab.jms.client.net.JmsSessionStubImpl__Proxy.onMessage(JmsSessionStub
Impl__Proxy.java:249)
 at
org.exolab.jms.server.JmsServerSession.onMessage(JmsServerSession.java:696)
 at org.exolab.jms.messagemgr.QueueConsumerEndpoint.deliverMessages
(QueueConsumerEndpoint.java:266)
 at
org.exolab.jms.messagemgr.AbstractConsumerEndpoint.run(AbstractConsumerEndpo
int.java:309)
 at
org.exolab.jms.common.threads.ThreadPoolWorker.runIt(ThreadPoolWorker.java:1
92)
 at
org.exolab.jms.common.threads.ThreadPoolWorker.runWork(ThreadPoolWorker.java
:177)
 at
org.exolab.jms.common.threads.ThreadPoolWorker.access$000(ThreadPoolWorker.j
ava:64)
 at org.exolab.jms.common.threads.ThreadPoolWorker$1.run
(ThreadPoolWorker.java:119)
 at java.lang.Thread.run(Thread.java:534)
 
 
please help in this regard ...................................