- Are you having problems with Application Servers being unexpectedly
restarted by the node agent? This means that you are not sure why the node
agent lost contact with the Application Server and restarted it.
- Are you having problems with the node agent stopping Application
Servers but not restarting them? This means that you are aware that the
node agent is forcing the Application Servers to stop, but are not sure
why the Application Servers are not being restarted.
- Are you experiencing problems with Application Servers not starting
properly when the node agent is started? This means when the node agent is
started, the AppServers on that node are not following the
NodeRestartState setting.
These are the Troubleshooting questions for problems where your
Application Server is unexpectedly restarted.
- Does the node agent SystemOut.log file contain any messages
around the time of the Application Server restart, with message IDs
ADML0063W and ADML0064I?
- Check the Application Server SystemOut.log and
SystemErr.log for any messages indicating why the node agent may
not have been able to contact the Application Server. An
OutOfMemory or Hang condition or a network outage might explain
this behavior.
- If you are a V5.0 or V5.1 user and the Application Server appears to
have been running fine, ensure you are at 5.0.2.7 or 5.1.0.5, or a higher
level. If not then this is most likely caused by PQ89772.
- If the Application Server is hung, the node agent will be unable to
contact it and may eventually hang also. If you experience this problem it
is likely due to PK22291.
- If none of the preceding troubleshooting steps helped resolve your
problem, see the MustGather
for node agent monitoring Application Server problems.
These are the Troubleshooting questions for problems where your
Application Server was stopped by the node agent but NOT restarted. If
this happens you will see the "ADML0063W" message in the node agent
SystemOut.log but not the "ADML0064I" message indicating
the Application Server was restarted.
- If you are running V6.0 or V6.1, this is most likely caused by PK28095
which was fixed in 6.0.2.17 and 6.1.0.3.
- If you are running V5.0 or V5.1, this is most likely caused by PK16645
which was fixed in 5.0.2.16 and 5.1.1.10.
These are the Troubleshooting questions for problems where your
Application server was not started when the node agent was started.
- When the node agent starts up, does the Application Server fail to
start?
- Yes, check the NodeRestartState setting under
Servers > Application Servers > server_name. Then, under
Server Infrastructure, click Java™ and Process Management > Monitoring
Policy.
- If this is set to STOPPED then this behavior is expected. Please
change to either PREVIOUS or RUNNING.
- If this is set to PREVIOUS then the Application Server should return
to the same state when the node agent was last stopped. If the Application
Server was previously running and does not start, please see question 2
- If this is set to RUNNING, then please see question 2
- No, continue to question 3.
- Is your Application Server set to start when the node agent starts,
but does not actually do this?
- Yes, ensure your WebSphere Application Server level
is greater than 5.1.1.9 or 5.0.2.16. If it is not then APAR
PK16066 is likely the cause of this problem. (Users of all releases of
V6.0 do not have this problem).
- No, continue to the next question.
- If none of the preceding troubleshooting steps helped resolve your
problem, see the MustGather
for node agent monitoring application server problems.
|