com.dotcms.repackage.org.elasticsearch.common.util.concurrent.EsExecutors$ExecutorScalingQueue

Google Groups | Unknown author | 2 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    CPU Loading High - Lock find in elastic search

    Google Groups | 2 years ago | Unknown author
    com.dotcms.repackage.org.elasticsearch.common.util.concurrent.EsExecutors$ExecutorScalingQueue

    Root Cause Analysis

    1. com.dotcms.repackage.org.elasticsearch.common.util.concurrent.EsExecutors$ExecutorScalingQueue

      No message provided

      at java.util.concurrent.locks.LockSupport.park()
    2. Java RT
      LockSupport.park
      1. java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
      1 frame
    3. com.dotcms.repackage
      LinkedTransferQueue.take
      1. com.dotcms.repackage.org.elasticsearch.common.util.concurrent.jsr166y.LinkedTransferQueue.awaitMatch(LinkedTransferQueue.java:706)
      2. com.dotcms.repackage.org.elasticsearch.common.util.concurrent.jsr166y.LinkedTransferQueue.xfer(LinkedTransferQueue.java:615)
      3. com.dotcms.repackage.org.elasticsearch.common.util.concurrent.jsr166y.LinkedTransferQueue.take(LinkedTransferQueue.java:1109)
      3 frames
    4. Java RT
      Thread.run
      1. java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
      2. java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
      3. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
      4. java.lang.Thread.run(Thread.java:745)
      4 frames