Huge number of threads like "pool-XXXX-thread-1" (WF 8.2)

[atchijov-vgw]

HI,

     I wonder if anybody can help me with this issue. Recently I start noticing that number of threads in my Wildfly 8.2 keep growing and growing... when I run jstack I have noticed bunch of threads like this:

"pool-16609-thread-1" prio=10 tid=0x00007f1d0327a000 nid=0x5433 waiting on condition [0x00007f1ad23a2000]
   java.lang.Thread.State: WAITING (parking)
    at sun.misc.Unsafe.park(Native Method)
    - parking to wait for  <0x000000059b1ae630> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
    at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
    at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
    at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1079)
    at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807)
    at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:745)

     Your help will be highly appreciated.

Cheers,

  Andrei

[marcial.atienzar]

I've the same issue. I'm my case, I think it is produced by the use of jasperreports, but in others threads that I've read, they say that may be cause for the use of @Scheduller. Sorry but I can't find a solution yet. I've found one, I tell you.