Problem: Unable to stop a server process

You are trying to stop an application server through the administrative console but are getting failure messages.

 

àData to collect:

The following logs and output can be helpful in determining why you cannot stop an application server:

Deployment manager:      SystemOut.log, SystemErr.log
Node agent:                         SystemOut.log, SystemErr.log
Application Server:             SystemOut.log, SystemErr.log

 If you are trying to manage a server using a management script, such as
stopServer.bat, then you need the log file from that script (stopServer.log) and possibly a trace of that script.

 

àWhat to look for:

Figure 4-6 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.

Ex Fig 4-6 Administrative console error stopping an application server anode/server02 has not been started.

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 nodeagent, you might see messages similar to those that are shown in Example 4-10.

Example 4-10 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, as shown in Example 4-11.

Example 4-11 Hung node agent error messages

—————————————————————-

[7/11/05 14:19:00:918 EDT] 0000000f ThreadMonitor W WSVR0605W: Thread “WebContainer : 1″ (00000038) has been active for 619290 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be 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. You can get the process ID of the server from startServer.log in the server’s logs directory. Make sure you scroll to the end of the file to get the process ID from the latest start.

à        In a Windows environment, you can use the Task Manager to stop the task. à         In a UNIX environment, you can use the kill command to kill the Java process. After you have killed the hung Java process, you need to restart the server.

Stopping a hung process is simply a work-around. The real problem is the hang.