Top reports that the java process running the weblogic appserver on reedi is running at high cpu usage:
24548 root 88 0 0 878M 662M cpu/0 68.4H 46.97% java
Normal cpu usage is between 5% and 10%.
Looking at the nohup.log for reedi, we see the stuck thread message:
<Dec 11, 2006 10:51:32 AM PST> <Warning> <WebLogicServer> <BEA-000337> <ExecuteThread: '7' for queue: 'weblogic.kernel.Default' has been busy for "600" seconds working on the request "Http Request: /ptagis/loginAction.jsp", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
This calls for a restart of the appserver.
Ask for a graceful restart of appserver_reedi from the weblogic admin gui. If the admin gui is unresponsive (because it can't talk to the stuck thread), you may be forced to use a kill or kill -9 on the java process on reedi.
Then restart the weblogic appserver.
how can we resolve the stuck threads? what's the configured value in web logic server? is it 600 sec..if we either increase/decreased what happens? due to more stuck threads we are restarting the server...do we have any solution with restart rectify problem?
ReplyDeletealso y using ' Ctrl +break ' buttons in window os? is this correct command or configuration? i tried this ..but no response..please correct me regarding thread dumps in windows Env....Thank u