It's not a secret anymore!
The moose likes BEA/Weblogic and the fly likes Stuck Thread Problem in Weblogic &  DB2 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Stuck Thread Problem in Weblogic &  DB2" Watch "Stuck Thread Problem in Weblogic &  DB2" New topic

Stuck Thread Problem in Weblogic & DB2

Lakshmi Sindhura

Joined: Oct 09, 2012
Posts: 1
Hi ,

Please help us in analysing the below Stuck Thread Dump.In our webapplication we are using Java and DB2.
When we are trying to submit a request we are getting the below error:

Accept: image/gif, image/jpeg, image/pjpeg, image/pjpeg, application/x-shockwave-flash, application/xaml+xml, application/x-ms-xbap, application/x-ms-application, application/, application/, application/, application/msword, */*
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET4.0C; .NET4.0E; MS-RTC LM 8; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; InfoPath.2)
Content-Type: application/x-www-form-urlencoded
Accept-Encoding: gzip, deflate
Content-Length: 1027
Connection: Keep-Alive
Cache-Control: no-cache
Cookie: JSESSIONID=gxdbQkJKc1nyynt3fys9mkNHtSxHvTC68kSQjQ0yQQ0VG0QQVTQq!2045462985

]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-98 "

[STUCK] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'"
<alive, in native, suspended, priority=1, DAEMON> {
^-- Holding lock:[thin lock]
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(Unknown Source)
weblogic.servlet.internal.WebAppServletContext$ Source)
weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source)
weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source) Source)

Please help us in understanding the log as soon as possible.

Carol Enderlin
Ranch Hand

Joined: Oct 10, 2000
Posts: 1364
What is to understand? It looks like some class of yours is calling execute on a PreparedStatement. Is there a problem with the query?

From stack trace :

German Gonzalez-Morris
Ranch Hand

Joined: Nov 16, 2009
Posts: 232

it is a timeout message of you stuck thread. It can be even a long-runner query and the message is being thrown before returns it.
if it is necessary then you can set a longer timeout.

As you know can be several issues, therefore try to execute the same SQL queries outside of WLS, and check if you can replicate the issue.
I agree. Here's the link:
subject: Stuck Thread Problem in Weblogic & DB2
It's not a secret anymore!