Databases
StackOverflow2013
Postsdbo
POjava thread hanging causing other threads to hang (continued)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POjava thread hanging causing other threads to hang (continued)
    primarykey
    data
    text
    <p>I managed to generate thread dump when my test case hanging. However, it doesn't seemed to be a deadlock, a race condition or resource contention. But it definitedly hung while running the test case in my loading testing tool with 3 virtual users. Anyone can point me to the right direction here? Cheers</p> <pre><code>"Servlet.Engine.Transports : 387" daemon prio=5 tid=0x15386f8 nid=0x943 waiting on monitor [0xb4781000..0xb4781a00] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:415) at com.ibm.ws.util.BoundedBuffer.take(BoundedBuffer.java:161) at com.ibm.ws.util.ThreadPool.getTask(ThreadPool.java:422) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:669) "Servlet.Engine.Transports : 385" daemon prio=5 tid=0x51e898 nid=0x93e waiting on monitor [0xb3281000..0xb3281a00] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:415) at com.ibm.ws.util.BoundedBuffer.take(BoundedBuffer.java:161) at com.ibm.ws.util.ThreadPool.getTask(ThreadPool.java:422) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:669) "Servlet.Engine.Transports : 384" daemon prio=5 tid=0x464760 nid=0x93d waiting on monitor [0xb3381000..0xb3381a00] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:415) at com.ibm.ws.util.BoundedBuffer.take(BoundedBuffer.java:161) at com.ibm.ws.util.ThreadPool.getTask(ThreadPool.java:422) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:669) "Servlet.Engine.Transports : 382" daemon prio=5 tid=0x1141de8 nid=0x8a0 waiting on monitor [0xb3581000..0xb3581a00] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:415) at com.ibm.ws.util.BoundedBuffer.take(BoundedBuffer.java:161) at com.ibm.ws.util.ThreadPool.getTask(ThreadPool.java:422) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:669) "Servlet.Engine.Transports : 380" daemon prio=5 tid=0x1151ad8 nid=0x6b5 waiting on monitor [0xb3e81000..0xb3e81a00] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:415) at com.ibm.ws.util.BoundedBuffer.take(BoundedBuffer.java:161) at com.ibm.ws.util.ThreadPool.getTask(ThreadPool.java:422) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:669) "Servlet.Engine.Transports : 366" daemon prio=5 tid=0x1a1d110 nid=0x3fb waiting on monitor [0xb4b81000..0xb4b81a00] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:415) at com.ibm.ws.util.BoundedBuffer.take(BoundedBuffer.java:161) at com.ibm.ws.util.ThreadPool.getTask(ThreadPool.java:422) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:669) "Servlet.Engine.Transports : 365" daemon prio=5 tid=0x4e8bd8 nid=0x3fa waiting on monitor [0xb6281000..0xb6281a00] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:415) at com.ibm.ws.util.BoundedBuffer.take(BoundedBuffer.java:161) at com.ibm.ws.util.ThreadPool.getTask(ThreadPool.java:422) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:669) "Servlet.Engine.Transports : 362" daemon prio=5 tid=0x17055b0 nid=0x3f7 waiting on monitor [0xb3481000..0xb3481a00] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:415) at com.ibm.ws.util.BoundedBuffer.take(BoundedBuffer.java:161) at com.ibm.ws.util.ThreadPool.getTask(ThreadPool.java:422) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:669) "Servlet.Engine.Transports : 356" daemon prio=5 tid=0x1ddbae0 nid=0x3f1 waiting on monitor [0xb9c01000..0xb9c01a00] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:415) at com.ibm.ws.util.BoundedBuffer.take(BoundedBuffer.java:161) at com.ibm.ws.util.ThreadPool.getTask(ThreadPool.java:422) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:669) "Servlet.Engine.Transports : 299" daemon prio=5 tid=0x2519028 nid=0x3b5 waiting on monitor [0xb6001000..0xb6001a00] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:415) at com.ibm.ws.util.BoundedBuffer.take(BoundedBuffer.java:161) at com.ibm.ws.util.ThreadPool.getTask(ThreadPool.java:422) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:669) </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USOrtwin Angermeier
    1. USdale
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POjava thread hanging causing other threads to hang (continued)
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    2. VO
      singulars
      1. POjava thread hanging causing other threads to hang (continued)
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSeeing the code might help... Your threads are waiting on a Buffer, are you sure it's not empty?
      singulars
      1. POjava thread hanging causing other threads to hang (continued)
      1. USDmitri
    2. COI think the question in its current form is unanswerable. There simply ins't enough information.
      singulars
      1. POjava thread hanging causing other threads to hang (continued)
      1. USNPE
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload