Threads are blocked and application became unresponsive. Please advise

Hi Manoj!

If threads are BLOCKED for a prolonged period, your application may become unresponsive. Examine their stack trace.

You can find that stack trace in the section "Threads with identical stack trace":

Some threads are stuck and before getting stuck, those threads obtained some locks. Following is the detail:

Hi Manoj,

And also "6 threads" are in a STUCK state. Threads that are taken out of the pool and not returned after a specified time period are marked as STUCK threads. It may or may not be a problem. Study their stack trace to understand its behavior.

Following is the 6 STUCK threads:

1. [STUCK] ExecuteThread: '148' for queue: 'weblogic.kernel.Default (self-tuning)'
2. [STUCK] ExecuteThread: '61' for queue: 'weblogic.kernel.Default (self-tuning)'
3. [STUCK] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'
4. [STUCK] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'
5. [STUCK] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'
6. [STUCK] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'

stackTrace:
at df.JadePage.parseLIST(JadePage.java:1201)
at df.JadePage.LoadPage(JadePage.java:397)
at df.JadePage.LoadPage(JadePage.java:220)
at df.JadePage.SetHTMLCode(JadePage.java:576)
at df.JadePage.LoadPage(JadePage.java:361)
at df.JadePage.SetHTMLCode(JadePage.java:576)
at df.JadePage.LoadPage(JadePage.java:361)
at df.Framework.Execute(Framework.java:297)
at jsp_servlet.__server._jspService(__server.java:645)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:35)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:280)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:254)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:136)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:346)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:25)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at ResponseHeaderFilter.doFilter(ResponseHeaderFilter.java:33)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3456)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3422)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:323)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)
at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2280)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2196)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1632)
at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:256)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)