Wednesday, June 11, 2014

Weblogic Managed server status struck in STARTING

Weblogic Managed server status struck in STARTING

We faced the issue while starting the weblogic managed server the status of the server struck in STARTING.
W could not able to find a valid error messages in the log files
Managed Server Log File:
<11-Jun-2014 11:13:29 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING> 
No logs are getting printed after this.
Node Manager Log File:
<11-Jun-2014 11:09:44> <INFO> <POCDomain> <MS1> <Server failed during startup so will not be restarted>
<11-Jun-2014 11:09:44> <WARNING> <Exception while starting server 'MS1'>
java.io.IOException: Server failed to start up. See server output log for more details.
      at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
      at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
      at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
      at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
      at weblogic.nodemanager.server.Handler.run(Handler.java:71)
      at java.lang.Thread.run(Thread.java:662)
The root cause of this issue is somehow the ldap directory of the server got corrupted.
To resolve this issue:
 Kill the managed server 
 Remove the ldap folder from the following location  <<DOMAIN_HOME>>/servers/<<Managed Server>>, this file will 

 be auto generated while restarting the server.
Restart the server

No comments:

Post a Comment