[xgws-user] WS-Messenger UnSubcriptions

Tue, 03 Apr 2007 17:45:38 +0200

Hi,

A little more information. When "CleanUpThread" has to remove an old 
subscription I get the same error:

Exception in thread "Thread-3" java.lang.NullPointerException
        at 
wsmg.adapter.XPath.YFilterInfo.removeSubscription(YFilterInfo.java:85)
        at 
wsmg.adapter.XPath.YFilterAdapter.handleUnsubscribe(YFilterAdapter.java:175)
        at 
wsmg.processors.SubscriptionManager.removeSubscription(SubscriptionManager.java:556)
        at 
wsmg.processors.SubscriptionManager.access$200(SubscriptionManager.java:61)
        at 
wsmg.processors.SubscriptionManager$CleanUpThread.run(SubscriptionManager.java:676)
        at java.lang.Thread.run(Unknown Source)

Thanks.

Alex Piqueras escribió:
> Hi all,
>
> I've found another strange behavior in unsubscriptions. When a client 
> subscribe and unsubscribe the same topic twice, i.e. Subscribe, 
> Unsubscribe, Subscribe, Unsubscribe.
> On second unsubscription a get the next stack trace:
>
> Exception in thread "AWT-EventQueue-0" 
> xsul.invoker.DynamicInfosetInvokerException: HTTP server error 500 
> Runtime exception when processing request connection398on12345 body="
> <html>
> <head>
> <title>Runtime exception when processing request connection398on12345: 
> null</title>
> </head>
> <body>
> <h1>Runtime exception when processing request connection398on12345: 
> null</h1>
> <p><pre>java.lang.NullPointerException&#13;
>        at 
> wsmg.adapter.XPath.YFilterInfo.removeSubscription(YFilterInfo.java:85)&#13; 
>
>        at 
> wsmg.adapter.XPath.YFilterAdapter.handleUnsubscribe(YFilterAdapter.java:174)&#13; 
>
>        at 
> wsmg.processors.SubscriptionManager.removeSubscription(SubscriptionManager.java:548)&#13; 
>
>        at 
> wsmg.processors.SubscriptionManager.unsubscribe(SubscriptionManager.java:533)&#13; 
>
>        at wsmg.WSMGService.executeSoapEnvelope(WSMGService.java:325)&#13;
>        at 
> wsmg.xsul.XSULDedicatedBrockerService.processHttpXml(XSULDedicatedBrockerService.java:180)&#13; 
>
>        at 
> xsul.processor.http.HttpDynamicInfosetProcessor.service(HttpDynamicInfosetProcessor.java:189)&#13; 
>
>        at 
> wsmg.xsul.XSULDedicatedBrockerService.service(XSULDedicatedBrockerService.java:257)&#13; 
>
>        at 
> xsul.processor.http.HttpDynamicInfosetProcessor$HdisServlet.service(HttpDynamicInfosetProcessor.java:267)&#13; 
>
>        at 
> xsul.http_server.impl.HttpMiniServerConnection.process(HttpMiniServerConnection.java:183)&#13; 
>
>        at 
> xsul.http_server.impl.HttpMiniServerConnection.run(HttpMiniServerConnection.java:112)&#13; 
>
>        at java.lang.Thread.run(Unknown Source)&#13;
> </pre></p>
> </body>
> </html>"
>        at 
> xsul.invoker.http.HttpDynamicInfosetInvoker.invokeXml(HttpDynamicInfosetInvoker.java:369) 
>
>        at xsul.ws_addressing.WsaInvoker.sendXml(WsaInvoker.java:318)
>        at 
> xsul.ws_addressing.WsaInvoker.invokeMessageOptimzed(WsaInvoker.java:233)
>        at 
> xsul.ws_addressing.WsaInvoker.invokeMessage(WsaInvoker.java:224)
>        at 
> wsmg.CommonClientProcessing.unSubscribe(CommonClientProcessing.java:314)
>        at wsmg.WseClientAPI.unSubscribe(WseClientAPI.java:53)
>
> The subscription info sent to the broker is okey, so I think this 
> error could be in broker.
> (I'm using WS Eventing API (WseClientAPI) and subscriptions with topic 
> and xpath condition).
>
> Thanks.
>

-- 
-------------------------------------------------------
Alejandro Piqueras Meseguer (apiqueras_at_dif.um.es)
Dept. Ingeniería de la Información y las Comunicaciones
Facultad de Informática
Universidad de Murcia 