This content has been marked as final. Show 2 replies
Did you observe
-- any communication issues between engine and data tier?
-- Did any engine got shutdown ?
Usually incase where in replica finds engine is not communicating well and/or is un-responsive for long time, it unlocks the callstates (essentially sessions) associated with the engine so that some other engine can work on that call. During that time the callstate is marked stale and most of time you see that error when other engine picks up the call.
Your scenario might be different. What else you see in logs around this message .,
Thanks for your reply, Anurag !!
There isn't any known communication issue between engine and data tiers.
None of the Engine Tier JVMs was shut down.
If I want to look further into the possibility of "Engine tier un-responsive for long time", would you please give any details as whats considered as long time etc..
In console log, I don't see anything else around this message, thats related to the error.
A quick search in engine's server log files also didn't give any info.
Also, can I safely assume that this error won't cause any trouble if another engine tier instance picks up the call ?
Edited by: kedar.ambekar on Feb 19, 2010 1:05 PM