They look like threads from the Resource Adapter thread pool that are simply waiting for work to do. If you have 500 in that state, that may indicate that your thread pool is larger that it needs to be. If you have stuff waiting to be processed in ActiveMQ, and you still have all the resource adapter threads idle, then that would indicate an issue that we ought to investigate further.
Jon On Wed, Jul 8, 2020 at 9:39 AM Dignesh <[email protected]> wrote: > Hi, > > I am using 7.0.2 version of TomEE. I notice lot of worker threads (around > 500) in timed waiting state. Below is observed in thread stack trace in > thread dumps. These threads are in the same state for hours. Any specific > reason why the threads are in timed waiting state for such long time ? > > > JmsResourceAdapter-worker- - 1189 > priority:5 - threadId:0x00007f4578006800 - nativeId:0x4ddd - nativeId > (decimal):19933 - state:TIMED_WAITING > stackTrace: > java.lang.Thread.State: TIMED_WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000003ec4197f0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) > at > > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078) > at > java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467) > at > > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1073) > at > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Locked ownable synchronizers: > - None > > > > -- > Sent from: > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html >
