| commit | f2c4e5230ec553b0fc5958cee3572b1849588bb8 | [log] [tgz] |
|---|---|---|
| author | Radek Felcman <radek.felcman@oracle.com> | Fri Apr 09 12:52:26 2021 +0200 |
| committer | GitHub <noreply@github.com> | Fri Apr 09 12:52:26 2021 +0200 |
| tree | 4aa1ee1d913d6e781458ef067a472f37ea730e5b | |
| parent | e31af7e5f9653df2b53a0da52d899393b2ac7121 [diff] |
Extended logging of JPA L2 cache usage with thread info. (#1065) This commit contains extension to the EclipseLink logging to print information about persistence cache operations and usage. It prints info when entity is stored, refreshed, removed, invalidated in the cache and info about cache hits/miss. This feature is controlled by new "eclipselink.cache.extended.logging property" and generates messages at the FINEST log level. It prints additional message if one thread stored item into cache and different picking item. Signed-off-by: Radek Felcman <radek.felcman@oracle.com>
EclipseLink 3.0.0 
EclipseLink 2.7.x 
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.