Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

We are facing trouble with BEA-000337 error, can some one help?

Status
Not open for further replies.

bips22

Programmer
Nov 19, 2007
1
US
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
 
can you collect the thread dump and diagnostics and analyse the thread dump through samurai, Also if possible try to enable the core dump from OS side.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top