Hi David,
it seems that your use case does create/destroy/create/destroy....
topics with same 'oid', and that there is a multi-threading gap in
xmlBlaster with this use case
(the topic is shutdown while another thread is still operating on it).
Could you please send to me directly the complete log file?
thank you
Marcel
David Kerry wrote:
Hello all,
We just ran into another exception in the server that seems to have totally
confused
our clients:
Jun 28, 2006 8:41:17 AM org.xmlBlaster.engine.AvailabilityChecker checkException
SEVERE: publishArr() failed: XmlBlasterException serverSideException=true
node=[xmlBlaster_172_23_254_15_10412] location=[TopicHandler]
java.lang.NullPointerException
stackTrace=java.lang.NullPointerException
at org.xmlBlaster.authentication.SessionInfo.toXml(SessionInfo.java:594)
at
org.xmlBlaster.engine.TopicHandler.checkIfAllowedToSend(TopicHandler.java:1219)
at
org.xmlBlaster.engine.TopicHandler.invokeCallback(TopicHandler.java:1342)
at
org.xmlBlaster.engine.TopicHandler.invokeCallbackAndHandleFailure(TopicHandler.java:1202)
at org.xmlBlaster.engine.TopicHandler.publish(TopicHandler.java:660)
at org.xmlBlaster.engine.RequestBroker.publish(RequestBroker.java:1704)
at org.xmlBlaster.engine.RequestBroker.publish(RequestBroker.java:1495)
at org.xmlBlaster.engine.RequestBroker.publish(RequestBroker.java:1489)
at
org.xmlBlaster.engine.XmlBlasterImpl.publishArr(XmlBlasterImpl.java:198)
at
org.xmlBlaster.util.protocol.RequestReplyExecutor.receiveReply(RequestReplyExecutor.java:405)
at
org.xmlBlaster.protocol.socket.HandleClient.handleMessage(HandleClient.java:232)
at
org.xmlBlaster.protocol.socket.HandleClient.run(HandleClient.java:354)
at java.lang.Thread.run(Thread.java:595)
errorCode=internal.unknown message=#15171M This is an unknown and unexpected
error, usually a Java runtime exception, please post it to the mailing list. ->
http://www.xmlblaster.org/xmlBlaster/doc/requirements/admin.errorcodes.listing.html#internal.unknown
at org.xmlBlaster.engine.TopicHandler.publish(TopicHandler.java:669)
at org.xmlBlaster.engine.RequestBroker.publish(RequestBroker.java:1704)
at org.xmlBlaster.engine.RequestBroker.publish(RequestBroker.java:1495)
at org.xmlBlaster.engine.RequestBroker.publish(RequestBroker.java:1489)
at
org.xmlBlaster.engine.XmlBlasterImpl.publishArr(XmlBlasterImpl.java:198)
at
org.xmlBlaster.util.protocol.RequestReplyExecutor.receiveReply(RequestReplyExecutor.java:405)
at
org.xmlBlaster.protocol.socket.HandleClient.handleMessage(HandleClient.java:232)
at
org.xmlBlaster.protocol.socket.HandleClient.run(HandleClient.java:354)
at java.lang.Thread.run(Thread.java:595)
versionInfo=version=1.2,revision=15171M,os.name=Linux,os.version=2.6.15.6,java.vm.vendor=Sun
Microsystems
Inc.,java.vm.version=1.5.0_06-b05,os.arch=i386,build.timestamp=05/24/2006 09:56
AM,build.java.vendor=Sun Microsystems Inc.,build.java.version=1.5.0_04
errorCode
description=http://www.xmlblaster.org/xmlBlaster/doc/requirements/admin.errorcodes.listing.html#internal.unknown
Jun 28, 2006 8:41:17 AM org.xmlBlaster.protocol.socket.HandleClient
handleMessage
FINE: Can't handle message, throwing exception back to client:
errorCode=internal.unknown message=#15171M This is an unknown and unexpected
error, usually a Java runtime exception, please post it to the mailing list. ->
http://www.xmlblaster.org/xmlBlaster/doc/requirements/admin.errorcodes.listing.html#internal.unknown
:
java.lang.NullPointerException
Also, since I'm here - any word on resolving some of the other
multi-thread race issues we keep banging into? For some reason,
our access patterns seem to expose them more than anyone else it seems.
