Re: [xmlblaster] NPE in ClientSubscriptions.getSubscriptionByOid

[Marcel Ruff <ruff at swand.lake.de>]

Russell Chan wrote:

>Hi,
>
>I'm using XMLBlaster 0.80.  I'm getting a NPE in
>ClientSubscriptions.getSubscriptionByOid...
>
>
>
>[Oct 18, 2002 4:44:50 PM ERROR
>CbWorker-/node/http:10.0.1.157:3412/client/guest/3] Unexpected
>exception: java.lang.NullPointerException
>java.lang.NullPointerException
>	at
>org.xmlBlaster.engine.ClientSubscriptions.getSubscriptionByOid(ClientSubscriptions.java:210)
>	at
>org.xmlBlaster.engine.ClientSubscriptions.messageErase(ClientSubscriptions.java:285)
>	at
>org.xmlBlaster.engine.RequestBroker.fireMessageEraseEvent(RequestBroker.java:1669)
>	at
>org.xmlBlaster.engine.RequestBroker.eraseVolatile(RequestBroker.java:1318)
>	at
>org.xmlBlaster.engine.queue.MsgQueue.checkForVolatileErase(MsgQueue.java:212)
>	at org.xmlBlaster.engine.callback.CbWorker.run(CbWorker.java:61)
>	at
>EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:728)
>	at java.lang.Thread.run(Thread.java:498)
>
>
>All of my subscriptions are XPATH based, rather than OID based.. For
>example:
>
>SubscribeKeyWrapper subscribeKey = new
>SubscribeKeyWrapper(
>"//service[.=\""+EventQueueConstants.SERVICE_TEMPLATE_PARSE+"\" and "+
>                    "../type[.=\""+EventQueueConstants.TYPE_RESPONSE+"\"
>and "+
>                    "../id[.=\""+ eventQueueId+"\"]]]","XPATH");
>
>
>I'm using primarily volatile messages.  I see the NPE while the sweeper
>thread (for volatile messages) appears to be running.
>
>I'm going to attach a dump of the xmlblaster state.  I *DO* notice that
>even during a dump xmlblaster complains about the "Can't determine key
>oid" (See the top of the dump).
>
>I'm obviously doing something wrong here... Insights appreciated :-)
>
If there are NPEs its not you but xmlBlaster which is fishy.
Can you provide a little demo client reproducing this problem?

thanks

Marcel

>
>Russ
>
>PS. For what it's worth, it a linux debian woody environment with and
>IBM jdk 1.3 JVM (server & client).
>
>
>