Skip to content

thread struck issue for long time (possible dead lock ongoing) - concurrencyManagerCreationDate #2614

@Thanigaivelut

Description

@Thanigaivelut

Describe the bug
we are using eclipselink 2.7.11 version along with Spring and deployed in tomcat. We are facing thread struck issue without any error in logs sporadically and subsequently request fails after this thread stuck which requires a restart. We recieved an error in logs stating the request failed due to the given below and the threaddump in logs by the eclipselink for a failed request. Can you suggest a solution for this issue.

  • EclipseLink version 2.7.11
  • Java/JDK version 1.8.0_451

we are using eclipselink 2.7.11 version along with Spring and deployed in tomcat. We are faing thread struck issue without any error in logs and subsequently request fails after this thread stuck. We recieved an error in logs stating the request failed due to the given below and the threaddump in logs by the eclipselink for a failed request.

[EL Severe]:cache: 2025-12-15 05:25:31.386--Summary current cache key of thread http-nio-8026-exec-29 Stuck thread problem: unique tiny message number (1)
Dec 15, 2025 5:25:31 AM: [CMAX6-1] The Thread [http-nio-8026-exec-29] appears to be stuck (possible dead lock ongoing). The thread is working in the context of (CacheKey) = (--- CacheKey (com.lhs.Contract.bscs_core.Contract): (primaryKey: 191,966,917) (object: com.lhs.Contract.bscs_core.Contract@3fe69426) (object hash code: 1072075814) (cacheKeyClass: org.eclipse.persistence.internal.identitymaps.HardCacheWeakIdentityMap.ReferenceCacheKey) (cacheKey hash code: 1024451648) (current cache key owner/activeThread: Null) (getNumberOfReaders: 0) (concurrencyManagerId: 3,179,984) (concurrencyManagerCreationDate: 2025-12-15 05:10:30.827) (totalNumberOfTimeCacheKeyAcquiredForReading: 2) (totalNumberOfTimeCacheKeyReleasedForReading: 2) (totalNumberOfTimeCacheKeyReleasedForReadingBlewUpExceptionDueToCacheKeyHavingReachedCounterZero: 0) (depth: 0) ---) .
Dec 15, 2025 5:25:31 AM: [CMAX6-1] The thread has been stuck for: (264,692 ms)
Dec 15, 2025 5:25:31 AM: [CMAX6-1] Bellow we will describe the ActiveLocks, DeferredLocks and ReadLocks for this thread. Summary of active locks owned by thread http-nio-8026-exec-29 Listing of all ACTIVE Locks.
Dec 15, 2025 5:25:31 AM: [CMAX6-1] Thread Name: http-nio-8026-exec-29
Dec 15, 2025 5:25:31 AM: [CMAX6-1] 0 Active locks. The lockManager for this thread is null.
Dec 15, 2025 5:25:31 AM: [CMAX6-1]

Threaddump
Dec 15, 2025 5:25:31 AM: [CMAX6-1] Summary of deferred locks (could not be acquired and cause thread to wait for object building to complete) of thread http-nio-8026-exec-29 Listing of all DEFERRED Locks.
Dec 15, 2025 5:25:31 AM: [CMAX6-1] Thread Name: http-nio-8026-exec-29
Dec 15, 2025 5:25:31 AM: [CMAX6-1] 0 deferred locks. The lockManager for this thread is null. Dec 15, 2025 5:25:31 AM: [CMAX6-1] [EL Severe]: cache: 2025-12-15 05:25:31.501--Start full concurrency manager state (massive) dump No: 1
Dec 15, 2025 5:25:31 AM: [CMAX6-1] Concurrency manager - Page 01 start - thread dump about all threads at time of event
Dec 15, 2025 5:25:31 AM: [CMAX6-1] "ForkJoinPool.commonPool-worker-31"
Dec 15, 2025 5:25:31 AM: [CMAX6-1] java.lang.Thread.State: TIMED_WAITING
Dec 15, 2025 5:25:31 AM: [CMAX6-1] at sun.misc.Unsafe.park(Native Method)
Dec 15, 2025 5:25:31 AM: [CMAX6-1] at java.util.concurrent.ForkJoinPool.awaitWork(ForkJoinPool.java:1835)
Dec 15, 2025 5:25:31 AM: [CMAX6-1] at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1704)
Dec 15, 2025 5:25:31 AM: [CMAX6-1] at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:172)
Dec 15, 2025 5:25:31 AM: [CMAX6-1]
Dec 15, 2025 5:25:31 AM: [CMAX6-1] "jgroups-18647,BSCSChannel,hostname-port"
Dec 15, 2025 5:25:31 AM: [CMAX6-1] java.lang.Thread.State: WAITING
Dec 15, 2025 5:25:31 AM: [CMAX6-1] at sun.misc.Unsafe.park(Native Method)
Dec 15, 2025 5:25:31 AM: [CMAX6-1] at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
Dec 15, 2025 5:25:31 AM: [CMAX6-1] at java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:458)
Dec 15, 2025 5:25:31 AM: [CMAX6-1] at java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:362)
Dec 15, 2025 5:25:31 AM: [CMAX6-1] at java.util.concurrent.SynchronousQueue.take(SynchronousQueue.java:924)
Dec 15, 2025 5:25:31 AM: [CMAX6-1] at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
Dec 15, 2025 5:25:31 AM: [CMAX6-1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
Dec 15, 2025 5:25:31 AM: [CMAX6-1] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
Dec 15, 2025 5:25:31 AM: [CMAX6-1] at java.lang.Thread.run(Thread.java:750)

Dec 15, 2025 5:50:39 AM: [CMAX6-1] Concurrency manager - Page 01 end - thread dump about all threads at time of event
Dec 15, 2025 5:50:39 AM: [CMAX6-1] Concurrency manager - Page 03 start - information about threads waiting to acquire read cache keys
Dec 15, 2025 5:50:39 AM: [CMAX6-1] Total number of threads waiting to acquire read locks: 30

Dec 15, 2025 5:50:39 AM: [CMAX6-1] Concurrency manager - Page 03 end - information about threads waiting to acquire read cache keys
Dec 15, 2025 5:50:39 AM: [CMAX6-1] Concurrency manager - Page 04 start - information about threads waiting on release deferred locks (waiting for other thread to finish building the objects deferred)
Dec 15, 2025 5:50:39 AM: [CMAX6-1] Total number of threads waiting to acquire lock: 0
Dec 15, 2025 5:50:39 AM: [CMAX6-1]
Dec 15, 2025 5:50:39 AM: [CMAX6-1] Concurrency manager - Page 04 end - information about threads waiting on release deferred locks (waiting for other thread to finish building the objects deferred)
Dec 15, 2025 5:50:39 AM: [CMAX6-1] Concurrency manager - Page 05 start (currentThreadNumber: 1 of totalNumberOfThreads: 1) - detailed information about specific thread

Dec 15, 2025 5:50:39 AM: [CMAX6-1] Concurrency manager - Page 05 end (currentThreadNumber: 1 of totalNumberOfThreads: 1) - detailed information about specific thread
Dec 15, 2025 5:50:39 AM: [CMAX6-1] Concurrency manager - Page 06 start - information about cache keys and threads needing them
Dec 15, 2025 5:50:39 AM: [CMAX6-1] Total number of cacheKeys to describe: 2

Dec 15, 2025 5:25:31 AM: [CMAX6-1] Concurrency manager - Page 06 end - information about cache keys and threads needing them
Dec 15, 2025 5:25:31 AM: [CMAX6-1] Concurrency manager - Page 07 start - dead lock explanation
Dec 15, 2025 5:25:31 AM: [CMAX6-1] We were not able to determine to determine a set of threads that went into dead lock.deadlock algorithm took 11 ms to try to find deadlock.
Dec 15, 2025 5:25:31 AM: [CMAX6-1] Concurrency manager - Page 07 end - dead lock explanation
Dec 15, 2025 5:25:31 AM: [CMAX6-1] End full concurrency manager state (massive) dump No: 1

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions