My Oracle Support Banner

Dead Lock Issues (Doc ID 2979342.1)

Last updated on OCTOBER 10, 2023

Applies to:

Oracle TopLink - Version 14.1.1 and later
Information in this document applies to any platform.


The application code fails with deadlocks during runtime 

Caused By: Exception [EclipseLink-2001] (Eclipse Persistence Services - 2.7.6.v20200131-b7c997804f): org.eclipse.persistence.exceptions.ConcurrencyException
Exception Description: Wait was interrupted.
Message: [Summary current cache key of thread ForkJoinPool.commonPool-worker-55 Stuck thread problem: unique tiny message number (14)
 The Thread [ForkJoinPool.commonPool-worker-55] appears to be stuck (possible dead lock ongoing).

in addition following errors reported from the WLS logs
Caused By: java.sql.SQLIntegrityConstraintViolationException: ORA-00001

Same reported in github

Needing to modify the library to make sure that the CACHE_QUERY_FORCE_DEFERRED_LOCKS happens earlier than that line of code.
Impact: The deadlocks issue occurs during runtime and cannot be reproduced at will.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.