Originally posted by gaurav kumar:
Hi,
I m getting the following error while starting my server on Weblogic.
weblogic.nodemanager.NodeManagerException: [The request to start the server EBTApps1 of domain ebtdomain failed because the node manager did not hear from the managed server in the configured timeout period. Despite this, if the managed server has not failed, it will come up and the node manager will start monitoring it. To adjust this timeout so that the task does not fail prematurely, please refer to the node manager property ScavangerDelaySeconds (Default value : 180 seconds. Current value : 180 seconds).]
at weblogic.nodemanager.client.CommandInvoker.execute(CommandInvoker.java:233)
at weblogic.nodemanager.client.CommandInvoker.invoke(CommandInvoker.java:91)
at weblogic.nodemanager.client.NodeManagerClient.executeCommand(NodeManagerClient.java:161)
at weblogic.nodemanager.client.NodeManagerExecuteRequest.execute(NodeManagerRuntime.java:1641)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
No Exception Messages
Cud anyone please help me on that.
Gaurav
The server timeout is set to three minutes currently so if the server has not finished starting up after this time period then nodemanager considers it to have failed.
The question is wuld you normally expect the server to boot up within this time period? If the answer is yes then you will have to look in the managed server startup logs to find out what is going wrong.
If on the other hand you would not expect the server to fully boot up within three minutes then you could try increasing the the timeout period to a larger value.
