Hi,
We are getting BEA-000337 error sometimes causing deadlocks on some transactions. This lock doesnt get released until you restart the weblogic app server.
I could see one java process continuously running when this issue occurs. This particular thread get stuck and deosnt allow that process to complete in any way.
Is there any work around to kill this thread from weblogic console to avoid app server restart?
Please see my error logs
####<Nov 14, 2007 10:12:03 AM PST> <Warning> <WebLogicServer> <tlgascm> <myserver> <weblogic.health.CoreHealthMonitor> <<WLS Kernel>> <> <BEA-000337> <ExecuteThread: '5' for queue: 'weblogic.kernel.Default' has been busy for "1,249" seconds working on the request "Http Request: /yantra/console/wmsinventory.detail", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
Please provide your inputs.
Thanks in advance.
bips
We are getting BEA-000337 error sometimes causing deadlocks on some transactions. This lock doesnt get released until you restart the weblogic app server.
I could see one java process continuously running when this issue occurs. This particular thread get stuck and deosnt allow that process to complete in any way.
Is there any work around to kill this thread from weblogic console to avoid app server restart?
Please see my error logs
####<Nov 14, 2007 10:12:03 AM PST> <Warning> <WebLogicServer> <tlgascm> <myserver> <weblogic.health.CoreHealthMonitor> <<WLS Kernel>> <> <BEA-000337> <ExecuteThread: '5' for queue: 'weblogic.kernel.Default' has been busy for "1,249" seconds working on the request "Http Request: /yantra/console/wmsinventory.detail", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
Please provide your inputs.
Thanks in advance.
bips