Hi Brad, that does not look good. We will look at it in the next days. Regards Michele
Brad Clements wrote: > I have switched to version 1.3, enabled htpasswd authentication. > > Now, my clients (which used to work), do not work, because xmlBlaster dies on > the very first publish to my client. I am using socket protocol, non-ssl. > > Log shows this:: > > Oct 9, 2006 3:30:49 PM WARNING > 15-XmlBlaster.DispatchWorkerPool.xmlBlaster_192_168_1_4_3412-5 RL10 > org.xmlBlaster.engine.RequestBroker deadMessage: Generating dead message > 'callback:/node/xmlBlaster_192_168_1_4_3412/client/customs/1/NORM/1160422249486000000/xmlBlaster_192_168_1_4_3412-1160422249416000002' > from publisher=/node/xmlBlaster_192_168_1_4_3412/client/customs_client/-4 > because delivery failed: XmlBlasterException serverSideException=true > node=[xmlBlaster_192_168_1_4_3412] > location=[callback:/node/xmlBlaster_192_168_1_4_3412/client/customs/1] > java.lang.NullPointerException > stackTrace=java.lang.NullPointerException > at > org.xmlBlaster.engine.dispatch.CbDispatchConnection.doSend(CbDispatchConnection.java:253) > at > org.xmlBlaster.util.dispatch.DispatchConnection.send(DispatchConnection.java:231) > at > org.xmlBlaster.util.dispatch.DispatchConnectionsHandler.send(DispatchConnectionsHandler.java:430) > at > org.xmlBlaster.util.dispatch.DispatchWorker.run(DispatchWorker.java:160) > at > EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:727) > at java.lang.Thread.run(Thread.java:595) > errorCode=communication.noConnection.dead message=#exported The remote > connection is not established and we have given up to poll for it. -> > http://www.xmlblaster.org/xmlBlaster/doc/requirements/admin.errorcodes.listing.html#communication.noConnection.dead > at > org.xmlBlaster.util.dispatch.DispatchManager.handleWorkerException(DispatchManager.java:465) > at > org.xmlBlaster.util.dispatch.DispatchWorker.run(DispatchWorker.java:193) > at > EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:727) > at java.lang.Thread.run(Thread.java:595) > versionInfo=version=1.3,revision=exported,os.name=Linux,os.version=2.6.9-34.0.2.ELsmp,java.vm.vendor=Sun > Microsystems > Inc.,java.vm.version=1.5.0_05-b05,os.arch=i386,build.timestamp=09/10/2006 > 06:26 PM,build.java.vendor=Sun Microsystems Inc.,build.java.version=1.4.2_06 > errorCode > description=http://www.xmlblaster.org/xmlBlaster/doc/requirements/admin.errorcodes.listing.html#communication.noConnection.dead > > > ethereal shows that xmlblaster immediately closes the tcp connection, instead > of > sending the update message. > > Any idea how I can trace this down? > > Its the same setup as xmlblaster 1.2, except I enabled http authentication > (in > clients) and setup an htpasswd file. > > > > > >
