[3.0] Extended Thread logging - backport from master #1173
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ee4j#1100) This change makes log output less confusing as cached entity should be reused/picked by different threads. Signed-off-by: Radek Felcman <radek.felcman@oracle.com> (cherry picked from commit 66490c7)
There is change in log message severity and log category. This log message is also produced if persistence 'eclipselink.cache.extended.logging' is set to true. Signed-off-by: Radek Felcman <radek.felcman@oracle.com> (cherry picked from commit c9272ea)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is change in log message severity and log category. This log message is also produced if persistence
eclipselink.cache.extended.loggingis set to true instead of previous eclipselink.thread.extended.logging.This is backport from PRs #1100 and #1120 .