Q10) How to resolve the Unable to stop a server process:

Q10) How to resolve the Unable to stop a server process:

You are trying to stop an application server through the administrative console but are getting failure messages.
Figure shows the result that you would see in the administrative console if you tried to stop an application server that had hung. It takes some time for the stop request to time out.
In this case, the SystemOut.log for the deployment manager will most likely not contain any relevant messages. However, in the SystemOut.log for the node agent, you might see messages similar to those that are shown in Example Node agent error stopping an application server [7/11/05 13:51:54:207 EDT] 0000000d ThreadMonitor W WSVR0605W: Thread "SoapConnectorThreadPool : 6" (00000032) has been active for 607027 milliseconds and may be
hung. There is/are 1 thread(s) in total in the server that may be hung.

In this example, the problem is that the application server is hung and cannot respond to requests. You might also see a situation in which the node agent is
hung, In the case where the node agent is hung, the administrative console will eventually time out after at least 10 minutes. You will see a message in the
deployment manager’s SystemOut.log before the time out. If an application server is hung, you can stop it by killing the Java process