Administrative Console shows Application Server is Stopped, but SystemOut.log shows that it is Open for E-Business
 Technote (troubleshooting)
 
Problem(Abstract)
An application server is started using the WebSphere® Application Server Network Deployment administrative console. However, an error message indicates the server did not start. The SystemOut.log for this server shows that the server has started, but the console still shows a status of stopped.
 
Cause
This condition can be caused by a configuration setting for the application server.
[12/31/03 11:37:07:864 CST] 4d83f5cc JMXConnectors > initDiscovery
[12/31/03 11:37:07:864 CST] 4d83f5cc JMXConnectors < initDiscovery
[12/31/03 11:37:07:964 CST] 4d83f5cc WsServer A WSVR0001I: Server server1 open for e-business
The initDiscovery method immediately exits and never lets the nodeagent know that it has started.
 
Resolving the problem
Check the console under Application Servers > servername > Administration Services to see if the Standalone checkbox is checked.
In a Network Deployment environment, this should NOT be checked if you want to use the dmgr administrative console to administer the application server. If it is checked, the server doesl not participate in distributed administration (as configured).
  1. Clear the check,
  2. Save the configuration.
  3. Restart the application server.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Administrative Console (all non-scripting)
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1157004
IBM Group: Software Group
Modified date: Jan 6, 2004