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

Re: [xmlblaster] Missing messages



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)

-- 
David Kerry

On Thu, May 25, 2006 at 01:54:18PM -0400, David Kerry wrote:
> Hello All,
> 
> We've managed to quell all the recent exceptions we've been having
> with the head version of xmlblaster.  However, we're still experiencing
> a case of occasional lost messages.
> 
> Every once in a long while, we'll lose a message.  It gets published
> successfully by the client, but no subscribers are ever notified that
> they have a message and it seems to just disappear into the ether.
> 
> This may or may not be related to the race condition we found earlier
> in regards to topic handling (destroy/publish overlap).
> 
> In our environment, it seems to happen on average once to 3 times per
> day.
> 
> Below is the error message we see in the logs when it happens (starts at
> 'MsgUnitCache is unexpected null'):
> 
> 24-May-2006 6:50:13 PM org.xmlBlaster.engine.MsgUnitWrapper <init>
> FINE: Created new MsgUnitWrapper instance 'org.xmlBlaster.engine.MsgUnitWrapper at 17ff759' 
> 24-May-2006 6:50:13 PM org.xmlBlaster.engine.TopicHandler publish
> FINE: Message http_post/2006-05-24 18:50:13.758 handled, now we can send updates to all interested clients.
> 24-May-2006 6:50:13 PM org.xmlBlaster.engine.TopicHandler invokeCallbackAndHandleFailure
> FINE: Going to update dependent clients for http_post, subscriberMap.size() = 0
> 24-May-2006 6:50:13 PM org.xmlBlaster.engine.MsgUnitWrapper setReferenceCounter
> FINE: Reference count changed from 1 to 0, this='org.xmlBlaster.engine.MsgUnitWrapper at 17ff759'
> 24-May-2006 6:50:13 PM org.xmlBlaster.engine.TopicHandler entryDestroyed
> FINER: Entering entryDestroyed(http_post/2006-05-24 18:50:13.758)
> 24-May-2006 6:50:13 PM org.xmlBlaster.engine.TopicHandler entryDestroyed
> SEVERE: MsgUnitCache is unexpected null, topic: 
>  <TopicHandler id='xmlBlaster_172_23_254_15_10412/topic/http_post' state='UNCONFIGURED'>
>   <uniqueKey>http_post</uniqueKey>
>   <SubscriptionInfo id='__subId:client/edserver_prod1148479503488-1148505216017000001:1148511013813000000'/>
>   <newCreated>true</newCreated>
>  </TopicHandler>
> 
>  msgUnitWrapper is: 
>  <MsgUnitWrapper id='http_post/2006-05-24 18:50:13.758' referenceCount='0' state='DESTROYED'>
>  
>   <qos>
>    <sender>/node/xmlBlaster_172_23_254_15_10412/client/app_post/-10</sender>
>    <expiration lifeTime='0' forceDestroy='false'/>
>    <rcvTimestamp nanos='1148511013758000000'/>
>    <persistent>false</persistent>
>    <route>
>     <node id='xmlBlaster_172_23_254_15_10412' stratum='0' timestamp='1148511013758000000' dirtyRead='false'/>
>    </route>
>   </qos>
>  
>   <key oid='http_post' contentMime='text/xml'>
>     <service>http_post</service><type>response</type><id>68970E0FFFFFFE0E00F5C3A617D2D9A7</id><operation>post</operation>
>   </key>
>   <content type='String' encoding='base64'>base-64 content removed</content>
>  </MsgUnitWrapper>
> 24-May-2006 6:50:13 PM org.xmlBlaster.engine.TopicHandler toUnreferenced
> FINER: Entering toUnreferenced(oldState=UNCONFIGURED, onAdministrativeCreate=false)
> 24-May-2006 6:50:13 PM org.xmlBlaster.engine.TopicHandler toDead
> FINER: Entering toDead(oldState=UNREFERENCED)
> 
> -- 
> David Kerry
>