2 Replies Latest reply on Dec 13, 2016 12:33 PM by Jeremy Whiting

    HTTP connector threading policy: indefinite increasing?

    Nicoletta Triolo Newbie


      I was monitoring the thread count of my applications on Jboss EAP 6.1. I found that the number of thread waiting on this stack trace

      http-/" daemon prio=10 tid=0x00007fadf48a5800 nid=0x1184 in Object.wait() [0x00007fadbf138000]

         java.lang.Thread.State: WAITING (on object monitor)

          at java.lang.Object.wait(Native Method)

          - waiting on <0x000000079afc2390> (a org.apache.tomcat.util.net.JIoEndpoint$Worker)

          at java.lang.Object.wait(Object.java:485)

          at org.apache.tomcat.util.net.JIoEndpoint$Worker.await(JIoEndpoint.java:875)

          - locked <0x000000079afc2390> (a org.apache.tomcat.util.net.JIoEndpoint$Worker)

          at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:901)

          at java.lang.Thread.run(Thread.java:662)


         Locked ownable synchronizers:

          - None



      has increased by from 118 to 727 in the space of one week.

      On line I read that it is possible to define a thread pool for the http connector, but I have not found any documentation about the default behaviour (i.e. without configuring thread pool).

      It seems threads are created and not released after use. Is it possible? If yes, also configuring a thread pool with a maximum number of threads should not work because once reached the maximum number it will fail attempting to create the maximum +1 thread.


      Has someone ideas or pointers to give me?


      Thanks a lot