aspose file tools*
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
Author

Stuck Thread Problem in Weblogic & DB2

Lakshmi Sindhura
Greenhorn

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/vnd.ms-xpsdocument, application/vnd.ms-excel, application/vnd.ms-powerpoint, 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> {
jrockit.net.SocketNativeIO.readBytesPinned(SocketNativeIO.java:???)
jrockit.net.SocketNativeIO.socketRead(SocketNativeIO.java:24)
java.net.SocketInputStream.socketRead0(SocketInputStream.java:???)
java.net.SocketInputStream.read(SocketInputStream.java:107)
com.ibm.db2.jcc.t4.z.b(z.java:161)
com.ibm.db2.jcc.t4.z.c(z.java:253)
com.ibm.db2.jcc.t4.z.c(z.java:370)
com.ibm.db2.jcc.t4.z.v(z.java:1147)
com.ibm.db2.jcc.t4.cb.e(cb.java:96)
com.ibm.db2.jcc.t4.q.e(q.java:81)
com.ibm.db2.jcc.t4.rb.k(rb.java:160)
com.ibm.db2.jcc.am.gn.jb(gn.java:2188)
com.ibm.db2.jcc.am.hn.b(hn.java:3499)
com.ibm.db2.jcc.am.in.gc(in.java:111)
com.ibm.db2.jcc.am.in.execute(in.java:92)
^-- Holding lock: com.ibm.db2.jcc.t4.b@1e51e2f7[thin lock]
weblogic.jdbc.wrapper.PreparedStatement.execute(PreparedStatement.java:87)
com.one.somers.action.CorrectJSLAction.execute(CorrectJSLAction.java:64)
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:217)
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1481)
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
javax.servlet.http.HttpServlet.service(HttpServlet.java:700)
javax.servlet.http.HttpServlet.service(HttpServlet.java:815)
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:224)
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:108)
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:206)
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183)
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(Unknown Source)
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:308)
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:116)
weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source)
weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source)
weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:203)
weblogic.work.ExecuteThread.run(ExecuteThread.java:170)

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

Thanks
Sindhu
Carol Enderlin
drifter
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: 191

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.


http://devwebcl.blogspot.com/
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Stuck Thread Problem in Weblogic & DB2