Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EclipseLink » Eclipselink 2.6.9 - Select statements in Logs
Eclipselink 2.6.9 - Select statements in Logs [message #1856625] Mon, 19 December 2022 07:32 Go to next message
Sven Moschel is currently offline Sven MoschelFriend
Messages: 4
Registered: July 2015
Junior Member
We have an issue with some of our Select Statements and Eclipselink write logs about it to the server log. Having the logs is ok but we donĀ“t want to see the Select Statements there.

Example:
--ReadAllQuery(referenceClass=Person sql="SELECT ...."

The generated log entry is in Log Level "Warning " and describes an issue that an attribute is not included in a fetch group.

Is there any way to tell Eclipselink NOT to add the statements to the Log? I already tried "DefaultLogger" with log level "INFO"


<property name="eclipselink.logging.logger" value="DefaultLogger"/>
<property name="eclipselink.logging.level" value="INFO"/>


In addition "ServerLogger" (Weblogic) was also not working with Log Level "Info".

[Updated on: Mon, 19 December 2022 08:59]

Report message to a moderator

Re: Eclipselink 2.6.9 - Select statements in Logs [message #1856662 is a reply to message #1856625] Wed, 21 December 2022 16:08 Go to previous messageGo to next message
Chris Delahunt is currently offline Chris DelahuntFriend
Messages: 43
Registered: December 2021
Member
Hello,

ServerLogger sets EclipseLink to use the server's logging exclusively. The logger then is configured only through server options - most likely the Weblogic console, by the server itself - EclipseLink has no control over it. The eclipselink.logging.level and other logging parameters are only applicable to the DefaultLogger.
You might want to check https://wiki.eclipse.org/EclipseLink/Examples/JPA/Logging if you haven't seen it already, as it shows INFO allows all info warning and error log messages to get logged. If you are looking to filter out Warning level messages, you'll need to use logging.level of SEVERE or OFF for the category you are looking at filtering.

Best Regards,
Re: Eclipselink 2.6.9 - Select statements in Logs [message #1856664 is a reply to message #1856662] Wed, 21 December 2022 16:23 Go to previous messageGo to next message
Sven Moschel is currently offline Sven MoschelFriend
Messages: 4
Registered: July 2015
Junior Member
Thanks for your reply. It is ok to see the warning in the Log. But not ok to see the SQL statement listed in the Log. And this happens independent of Server/Default Logger.
Re: Eclipselink 2.6.9 - Select statements in Logs [message #1856988 is a reply to message #1856664] Wed, 11 January 2023 18:19 Go to previous message
Chris Delahunt is currently offline Chris DelahuntFriend
Messages: 43
Registered: December 2021
Member
I don't know what log you are looking at - maybe post the full log message and what you log settings you've enabled/disabled. Or just file a feature/bug if you think it is logging you don't want and cannot turn off with existing settings.

My guess is you are seeing the output of a ReadAllQuery being converted to a string, which is relevant to tell anyone having to debug this problem which query is having the issue, and help understand it and the problem without searching code. I don't know why it is there on warning, but as mentioned, you can up the log level to SEVERE or OFF to no longer see it for that category of logging.
Previous Topic:Wrong type returned for aggregate functions over date?
Next Topic:Migration from Eclipselink 3.0.2 to 4.0.0
Goto Forum:
  


Current Time: Mon Dec 04 12:19:00 GMT 2023

Powered by FUDForum. Page generated in 0.02440 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top