Wednesday, September 01, 2010

BEA-000337 stuck ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'

This is the error i got when i created a asynchronous BPEL process and tried to test it.

<Aug 31, 2010 5:57:59 PM IST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] Exe
cuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy
for "701" seconds working on the request "weblogic.servlet.internal.ServletRequ
estImpl@18cdcd0[
POST /sbconsole/testdialog.portal?_nfpb=true&_windowLabel=ServiceTestDialogPortl
et&ServiceTestDialogPortlet_actionOverride=%2Ftest%2FServiceRequestAction&_pageL
abel=ServiceTestDialogPage&ServiceTestDialogPortletaction=execute HTTP/1.1
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/533.4 (K
HTML, like Gecko) Chrome/5.0.375.127 Safari/533.4
Referer: http://localhost:7001/sbconsole/testdialog.portal?_nfpb=true&_pageLabel
=ServiceTestDialogPage&ServiceTestDialogPortletref_fullname=default%2Fcheck&Serv
iceTestDialogPortletref_type=BusinessService&ServiceTestDialogPortlet_actionOver
ride=/test/OpenTestDialog&_windowLabel=ServiceTestDialogPortlet
Content-Length: 2972
Cache-Control: max-age=0
Origin: http://localhost:7001
Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryPdF9YQitn9u5ME
8v
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,i
mage/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: ADMINCONSOLESESSION=MDnLM8vW97Yty19yK6hpH1BlgLJhFsS3v1pLRcpC1hK1Zhkdgs1s
!-299843404; WINDOW_JSP_ID=Test_ServiceRequest; WINDOW_X_POS=0; WINDOW_Y_POS=0

]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds


TO over come this issue i did the following set up and it worked for me.

Log in to admin console

http://host:port/console

choose the server

Go to configurtaion-->Tuning tab and increase the Stuck Thread Max Time: and Stuck Thread Timer Interval: to some higher value

Once chnages are done restart the server and check this issue.



No comments: