[JIRA] (IDP-1945) Excessive spring and hibernate logging
Vladimir Mencl (Jira)
jira at shibboleth.atlassian.net
Fri Apr 29 09:16:29 UTC 2022
Vladimir Mencl ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A9e33c654-fa34-43c9-a1c1-fcc1c32d3528 ) *commented* on IDP-1945 ( https://shibboleth.atlassian.net/browse/IDP-1945?atlOrigin=eyJpIjoiZjc2Y2ZjZWFmNWVlNGZjZTljZTQ0M2EzNGFjMGVmNjciLCJwIjoiaiJ9 )
Re: Excessive spring and hibernate logging ( https://shibboleth.atlassian.net/browse/IDP-1945?atlOrigin=eyJpIjoiZjc2Y2ZjZWFmNWVlNGZjZTljZTQ0M2EzNGFjMGVmNjciLCJwIjoiaiJ9 )
I’ve tried drilling into it and found that the messages are produced by the Tomcat process on stdout - independently of the logging controlled by Tomcat’s logging.properties
The catalina.out file is populated by capturing the process’s output (via systemd/journald/rsyslog) and redirecting it to this file … and that’s why its structure has two levels of timestamps and two separate log levels. (Info defaulted to the captured output, and DEBUG produced by the original logging).
I’m still trying to get to where that is logged from, whether it’s related to an updated dependency - and whether there is a way to suppress it.
Some of the spring DEBUG log messages report initialization of every bean defined in the IdP configuration - I’d hope that can be controlled from somewhere.
( https://shibboleth.atlassian.net/browse/IDP-1945#add-comment?atlOrigin=eyJpIjoiZjc2Y2ZjZWFmNWVlNGZjZTljZTQ0M2EzNGFjMGVmNjciLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/IDP-1945#add-comment?atlOrigin=eyJpIjoiZjc2Y2ZjZWFmNWVlNGZjZTljZTQ0M2EzNGFjMGVmNjciLCJwIjoiaiJ9 )
Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100198- sha1:0065a29 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220429/060bb6b1/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-e5141697-5508-4f0c-bb5a-35a1250f10a6
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220429/060bb6b1/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-7c7a7442-2be0-4086-abf9-971074bdcdc0
Type: image/png
Size: 425 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220429/060bb6b1/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-11a793a9-5e0b-4475-9981-9f01fc61983f
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220429/060bb6b1/attachment-0005.png>
More information about the commits
mailing list