They are just idling (imho), what you are looking for is a depth stack having SearchHandler, QueryComponent, IndexSearcher lines.
On Mon, Jun 19, 2023 at 2:53 PM Ron Haines <[email protected]> wrote: > did get a thread dump, via admin console, while full load test is running: > > Seeing a lot of these....most in the 300k-900k ms range....yes 300-900 > seconds. Any chance these are just idle threads, waiting for work? > > qtp1278319954-13565 (13565) > > > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@5a0f92c5 > > - [email protected]/jdk.internal.misc.Unsafe.park(Native Method) > - [email protected] > /java.util.concurrent.locks.LockSupport.parkNanos(Unknown > Source) > - [email protected] > /java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown > Source) > - > > org.eclipse.jetty.util.BlockingArrayQueue.poll(BlockingArrayQueue.java:382) > - > > > org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.idleJobPoll(QueuedThreadPool.java:974) > - > > > org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1018) > - [email protected]/java.lang.Thread.run(Unknown Source) > - > -- Sincerely yours Mikhail Khludnev
