commit | bdc6ed476fa36a8f418ab84c704a4bc69fb725c5 | [log] [tgz] |
---|---|---|
author | Radek Felcman <radek.felcman@oracle.com> | Tue Mar 23 11:06:19 2021 +0100 |
committer | GitHub <noreply@github.com> | Tue Mar 23 11:06:19 2021 +0100 |
tree | 949d92e204ddfc60db3e2cb2b2c6b29c2eea410d | |
parent | e9e1bfcf28f56ed41fcfe066c13697be720a2a93 [diff] |
ConcurrencyManager dead-lock detection diagnostic improvement 2.0 - semaphores (#1041) Semaphores to limit parallel access to ObjectBuilder and WriteLockManager This is second part of dead-lock detection diagnostic improvement 2.0 related with previous PR #1038 . Previous PR content was passive from point of the view of the EclipseLink code execution. This PR has has active component org.eclipse.persistence.internal.helper.ConcurrencySemaphore which should be used to control/limit how many threads should execute selected code. In this case is ConcurrencySemaphore used to limit parallel access to org.eclipse.persistence.internal.descriptors.ObjectBuilder and org.eclipse.persistence.internal.helper.WriteLockManager to prevent possible dead-lock issues there. If ConcurrencySemaphore will be active, there should be negative impact to the performance. By default ConcurrencySemaphore is disabled and must be enabled by persistence or system properties. Signed-off-by: Radek Felcman <radek.felcman@oracle.com>
The EclipseLink project's goal is to provide a complete persistence framework that is both comprehensive and universal. It will run in any Java environment and read and write objects to virtually any type of data source, including relational databases, XML, JSON, or EIS systems. EclipseLink will focus on providing leading edge support, including advanced feature extensions, for the dominant persistence standards for each target data source; Jakarta Persistence for relational databases, Jakarta XML Binding for XML, Jakarta Connectors for EIS and other types of legacy systems, and Service Data Objects (SDO).
This project is part of the EclipseLink project.
EclipseLink is dual licensed under an EPL 2.0 and EDL 1.0 license.
We use contribution policy, which means we can only accept contributions under the terms of Eclipse Contributor Agreement.
Hint: If it‘s possible, it helps if some test reproducer is attached to the new bug. If it’s not possible, attached entities and persistence.xml file should help too for JPA related bugs. For MOXy, entities and XML or JSON resources/files are welcome.