This TroubleShooting document is applicable to
WebSphere Application Server Versions 5.0 and 5.1 on all platforms except
z/OS®.
Example for server JVMs
- AppServers (Ex:server1) and ClusterMembers
- jmsserver (only in federated Network Deployment)
- nodeAgent
- dmgr (Deployment Manager)
How to start a Server JVM
Any server JVM can be started from command
line using the startServer.sh/bat <serverName>
command. Additionally dmgr and nodeAgent can be started using specific
startNode and startManager. In Windows®, if the servers are already added
as Windows services then this can be started from the Windows services
Control Panel.
How to confirm the successful start of a JVM
No matter how the server start process is
executed, WebSphere Application Server always logs the start information
in
<WebSphere_Install_Root>/logs/<servername>/startServer.log.
ADMU3000I: Server <servername> open for e-business; process id is
<xxxxx>
Also WebSphere Application Server will create a PID file in the
<WebSphere_Install_Root>/logs/<servername>/ directory
with the corresponding server name, for example: server1.pid.
This PID file will have the PID for that server process. As long as the
PID is active this file will exist.
What to do if the server failed to start
If you do not see the above message in the
startServer.log and the corresponding PID file in the logs directory,
please review the
<WebSphere_Install_Root>/logs/<servername>/systemOut.log
for more information.
Are there any application start failures in systemOut.log?
Each application installed in that server
will try to start along with that server and will log the start process in
the systemOut.log, for example:
WSVR0200I: Starting application: MyApplication
WSVR0221I: Application started: MyApplication
Application start failure may result in server start failure. To narrow
down the issue please disable the application start during server start.
See Disabling
an enterprise application from starting when the application server
starts for more information.
Is there a port conflict, such as 'port in use' in the
systemOut.log?
Most of the time, a port conflict will
result in server failure. In this case you may see following message in
systemOut.log
ADMU3028I: Conflict detected on port xxxxx. Likely causes: a) An instance
of the server <MyServer> is already running. b) Some other process
is using port xxxxx.
In this case please make sure that there are no other processes using the
same port by doing netstat.
How to stop the server
Any server JVM can be stopped from the
command line using the stopServer.sh/bat <serverName>
command. Additionally dmgr and nodeAgent can be stopped
using specific stopNode and stopManager commands. With Security enabled,
the stopServer requires -username <username> and
-password <password> parameters in order to stop the
server.
How to confirm the successful stop of a JVM
No matter how the server stop process is
executed, WebSphere Application Server always logs the stop information in
<WebSphere_Install_Root>/logs/<servername>/stopServer.log
ADMU3201I: Server stop request issued. Waiting for stop status.
ADMU4000I: Server <MyServer> stop completed.
What to do when the server fails to stop
Server is started/stopped successfully but is not showing up in the
DeploymentManger console
What to do next
If the above steps did not solve your problem, please refer to the
following MustGather documents to continue investigation.
|