Check if the secondary server is down. Note that it is not recommended to kill both the primary and secondary server at the same time. Remember the replication happens lazily, upon request. So if you need to bring down the secondary server too give sufficient time so that the active end users hit their sessions and they get replicated.
But that does not tell me the possible causes of this in my environment. I know that anything could be the root cause of this problem, that it depends on many factors, all of them tied to my specific environment, but is there a general or basic cause of this problem?
Will you be able to see that these message time stamps has some pattern?
Like at a specific time ? Any idea if your Managed servers are being shutdown abruptly? seems to be mostly a message in Fail-over scenario.
Hareesh Ram Chanchali
SCJP 5.0, IBM Certified Solution Designer
Is cluster？do you config session replicated in you app?
the log seems to tell you that you put a object in session in the first server,when you get the object's value form the second server when the first one is going down.
in your weblogic.xml(between <weblogic-web-app> </weblogic-web-app>),but it must be cluster env.
Anyone can carry his burder,however hard,until nightfall.<br />Anyone can do his work,however hard,for one day.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com