Stopping Managed Server took hours

Question

Hi all,
I have an issue stopping the one of our managed servers (say MNG_SVR_1). It took almost 5 hrs to stop. There was no issue stopping another managed server.
In the managed server logs, I could see the following messages;
>
####<Jul 5, 2010 5:08:02 AM XXX> <Error> <Cluster> <XXXX10> <MNG_SVR_1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1278364082350> <BEA-000110> <Multicast socket receive error: java.lang.ClassNotFoundException: com.bea.p13n.cache.internal.system.CacheClusterMessage: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that cluster
java.lang.ClassNotFoundException: com.bea.p13n.cache.internal.system.CacheClusterMessage: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that cluster
at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:218)
at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:85)
at weblogic.common.internal.WLObjectInputStream.resolveClass(WLObjectInputStream.java:61)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1544)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.common.internal.WLObjectInputStream.readObjectWL(WLObjectInputStream.java:98)
at weblogic.cluster.MulticastReceiver.getNextMessage(MulticastReceiver.java:259)
at weblogic.cluster.MulticastReceiver.dispatch(MulticastReceiver.java:109)
at weblogic.cluster.MulticastManager.run(MulticastManager.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
I didn't have such issues previously. So, I am seeking some experts' advices on what went wrong.
Thanks in advance,
Stephen

Answer 1

How was the managed server tried to be brought down. Forceful or Graceful? In case of a graceful shutdown, the managed server would be brought down only after all the active requests are processed and completed. Moreover, there's something unusual that is seen in the logs that you pasted. Is some application component deployed on only one managed server of the cluster as the logs suggest??Few logs lines previous and after to the one that you have pasted would be giving more pointers...