[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xmlblaster] NullPointer exception



Hi David,

thank you for reporting.

The 'msgUnitStore' causing the NullPointer is never released in the code
so i assume it wasn't allocated properly in the topic initialization phase.

Is it possible you had a OutOfMemory exception somewhere before you
got your NullPointer?
Could you please check all your log files and System.err/System.out files for other ERROR reported?
Please mail to me directly more details if you find any.


I would recommend to start xmlBlaster with

  java -Dcom.sun.management.jmxremote org.xmlBlaster.Main

and observe it with 'jconsole'. Please check if all topics/clients are
as you would expect them in your environment or if any resources are growing
and are not freed as expected (jdk 1.5 only).

rgds,
Marcel


David Kerry wrote:

Hello,

We've been using the latest xmlblaster for a bit now and have started
getting these popping out once in a while in the logs:


[Sep 28, 2005 8:56:55 AM ERROR XmlBlaster.SOCKET.tcpListener-edserver_prod AvailabilityChecker] publishArr() failed: XmlBlasterException serverSideException=true node=[xmlBlaster_172_23_254_15_10412] location=[RequestBroker-/node/xmlBlaster_172_23_254_15_10412] java.lang.NullPointerException stackTrace=java.lang.NullPointerException at org.xmlBlaster.engine.TopicHandler.entryDestroyed(TopicHandler.java:946) at org.xmlBlaster.engine.MsgUnitWrapper.toDestroyed(MsgUnitWrapper.java:580) at org.xmlBlaster.engine.MsgUnitWrapper.setReferenceCounter(MsgUnitWrapper.java:309) at org.xmlBlaster.engine.TopicHandler.publish(TopicHandler.java:676) at org.xmlBlaster.engine.RequestBroker.publish(RequestBroker.java:1665) at org.xmlBlaster.engine.RequestBroker.publish(RequestBroker.java:1471) at org.xmlBlaster.engine.RequestBroker.publish(RequestBroker.java:1465) at org.xmlBlaster.engine.XmlBlasterImpl.publishArr(XmlBlasterImpl.java:194) at org.xmlBlaster.protocol.socket.Executor.receive(Executor.java:312) at org.xmlBlaster.protocol.socket.HandleClient.handleMessage(HandleClient.java:211) at org.xmlBlaster.protocol.socket.HandleClient.run(HandleClient.java:320) at java.lang.Thread.run(Thread.java:534) errorCode=internal.nullpointer message=#exported errorCode=internal.publish: An internal error occurred when processing a publish() request. /node/xmlBlaster_172_23_254_15_10412/client/edserver_prod/ -14 at org.xmlBlaster.util.XmlBlasterException.convert(XmlBlasterException.java:664) at org.xmlBlaster.util.XmlBlasterException.convert(XmlBlasterException.java:653) at org.xmlBlaster.engine.RequestBroker.publish(RequestBroker.java:1685) at org.xmlBlaster.engine.RequestBroker.publish(RequestBroker.java:1471) at org.xmlBlaster.engine.RequestBroker.publish(RequestBroker.java:1465) at org.xmlBlaster.engine.XmlBlasterImpl.publishArr(XmlBlasterImpl.java:194) at org.xmlBlaster.protocol.socket.Executor.receive(Executor.java:312) at org.xmlBlaster.protocol.socket.HandleClient.handleMessage(HandleClient.java:211) at org.xmlBlaster.protocol.socket.HandleClient.run(HandleClient.java:320) at java.lang.Thread.run(Thread.java:534) versionInfo=version=1.0.6,revision=exported,os.name=Linux,os.version=2.4.23,java.vm.vendor=Sun Microsystems Inc.,java.vm.version=1.4.2_03-b02,os.arch=i386,build.timestamp=08/10/2005 01:45 PM,build.ja va.vendor=Sun Microsystems Inc.,build.java.version=1.4.2_06 errorCode description=http://www.xmlblaster.org/xmlBlaster/doc/requirements/admin.errorcodes.listing.html#internal.nullpointer



Restarting xmlblaster makes it go away (for now), but I suspect it may
return.


While all this was going on, I also got errors from the client attempting to
subscribe. The error in the server log is:
[Oct 1, 2005 7:24:18 PM WARN XmlBlaster.SOCKET.tcpListener-core900_staging_ctb XmlKeyDom.InvalidQuery] Sorry, can't access, query syntax is wrong for '//service[.="ivs-123.com" and ../type[.="response"]]|//service[.="ivs-abc" and ../type[.="response"]]' : java.lang.NullPointerException


Since release 1.0.6+ (svn release #13727) we have a complete stack trace about this issue (if you ever upgrade)
which could probably help.


The error the client received was:

2005-10-01 19:24:18,358 ERROR [XmlBlaster.PingTimer] [logic.XmlBlasterSyncLogic]:  exception subscribing to messages:XmlBlasterException errorCode=[user.query.invalid] serverSideException=true location=[XmlKeyDom] message=[#exported Sorry, can't access, query syntax of '//service[.="ivs-123.com" and ../type[.="response"]]|//service[.="ivs-abc" and ../type[.="response"]]' is wrong : java.lang.NullPointerException] [See URL http://www.xmlblaster.org/xmlBlaster/doc/requirements/admin.errorcodes.listing.html#user.query.invalid]

errorCode=user.query.invalid message=#exported Sorry, can't access, query syntax of '//service[.="ivs-123.com" and ../type[.="response"]]|//service[.="ivs-abc" and ../type[.="response"]]' is wrong : java.lang.NullPointerException
       at org.xmlBlaster.util.XmlBlasterException.parseByteArr(XmlBlasterException.java:637)
       at org.xmlBlaster.protocol.socket.Parser.getException(Parser.java:482)
       at org.xmlBlaster.protocol.socket.Executor.receive(Executor.java:426)
       at org.xmlBlaster.client.protocol.socket.SocketCallbackImpl.run(SocketCallbackImpl.java:189)
       at java.lang.Thread.run(Thread.java:534)