Re: [xmlblaster] lostConnection in I_ConnectionProblems doesn't reportall

[Marcel Ruff]

Marcel Ruff wrote:
My xmlblaster setup uses lostConnection from I_ConnectionProblems to
implement a custom failo*ver strategy on the client side.
I noticed that sometimes when I shutdown the xmlblaster server
instance and the current connection is using XMLRPC, I get the
following exception on the client side, which does NOT get reported to
lostConnection():
[Mar 23, 2003 1:04:59 AM ERROR LoginThread-matighet] Unexpected 
exception while login polling: java.lang.NullPointerException
java.lang.NullPointerException
        at 
org.xmlBlaster.client.protocol.xmlrpc.XmlRpcConnection.initXmlRpcClient(XmlRpcConnection.java:90) 

        at 
org.xmlBlaster.client.protocol.xmlrpc.XmlRpcConnection.loginRaw(XmlRpcConnection.java:204) 

        at 
org.xmlBlaster.client.protocol.xmlrpc.XmlRpcConnection.loginRaw(XmlRpcConnection.java:193) 

        at 
org.xmlBlaster.client.protocol.XmlBlasterConnection.loginRaw(XmlBlasterConnection.java:956) 

        at 
org.xmlBlaster.client.protocol.XmlBlasterConnection.access$300(XmlBlasterConnection.java:118) 

        at 
org.xmlBlaster.client.protocol.XmlBlasterConnection$LoginThread.run(XmlBlasterConnection.java:2076) 



Furthermore, the connection seems to otherwise take publish calls just
fine (but obviously cannot deliver them).
I'll try upgrading to the latest CVS (just in case someone already
fixed it), as I'm running 2 weeks or so behind.
Hi Michael,

we will merge our development branch 'client_queue'
back to the main trunk today
(it will be announcend in the mailing list).
I think this issue should be resolved then.

regards,

Marcel

PS: Your mail got bounced because 'failo*ver' contains the banned
word 'lo*ve', we need to reconfigure majordomo i think :-)


Michael