Detecting and handling problems with run-time components
Why and when to perform this task
You must monitor the status of run-time components to ensure that,
once started, they remain operational as needed.
Steps for this task
Regularly examine the status of run-time components.
Browse messages displayed under Websphere Runtime Messages in the WebSphere status area at
the bottom of the console. The run-time event messages marked with a red X
provide detailed information on event processing.
If an application stops
running when it should be operational, examine the application's status on
an Applications page and
try restarting the application.
If messages indicate that a server has stopped running, use the Application Servers page to try restarting the server. If a cluster of servers has stopped
running, use the Server
Cluster page to try restarting
the cluster. If the status of an application server is Unavailable,
the node agent is not running in that node and you must restart the node
agent before you can start the server.
If the run-time components do not restart, re-examine the messages
and read information on problem determination to help you to restart the
components.
Searchable topic ID:
trun_watch_app Last updated: Jun 21, 2007 9:56:50 PM CDT
WebSphere Application Server for z/OS, Version 5.0.2 http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/trun_watch_app.html