[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xmlblaster] Missing messages

David Kerry wrote: 
Some more info on this...

Not sure if it will help, but I discovered this related exception in our logs
that is tied to this event as well:

java.lang.Exception: Stack trace
        at java.lang.Thread.dumpStack(Thread.java:1158)
        at org.xmlBlaster.engine.TopicHandler.entryDestroyed(TopicHandler.java:952)
        at org.xmlBlaster.engine.MsgUnitWrapper.toDestroyed(MsgUnitWrapper.java:596)
        at org.xmlBlaster.engine.MsgUnitWrapper.setReferenceCounter(MsgUnitWrapper.java:308)
        at org.xmlBlaster.engine.TopicHandler.publish(TopicHandler.java:681)
        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)
Yes, that is the stack trace which relates to the problem you described in your last mail.
This seems to be a multi threading issue during a topic is destroyed,
the traversed states are UNCONFIGURED -> UNREFERENCED -> DEAD

As a workaround you should keep the topic "http_post" alive (instead of create/delete/create/delete ... because of your volatile messages).
Please try to set

 -topic.destroyDelay 86400000

on xmlBlaster server command line or in xmlBlaster.properties (topic.destroyDelay=86400000)

I think it prevents your problem (but it is not a general fix yet).

regards
Marcel