[JIRA] (IDP-1945) Excessive spring and hibernate logging

[Scott Cantor (Jira)]

Scott Cantor ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5b78efc9-1379-42cc-a3f6-56c6ea3a0007 ) *commented* on IDP-1945 ( https://shibboleth.atlassian.net/browse/IDP-1945?atlOrigin=eyJpIjoiZGExYWRmNThiMzdiNGYxODg5ZWZjYzkwMjNkYTVmMWYiLCJwIjoiaiJ9 )

Re: Excessive spring and hibernate logging ( https://shibboleth.atlassian.net/browse/IDP-1945?atlOrigin=eyJpIjoiZGExYWRmNThiMzdiNGYxODg5ZWZjYzkwMjNkYTVmMWYiLCJwIjoiaiJ9 )

Spring logs through JCL as far as I know. We provide a bridge from that to SLF4J so that you may control Spring logging, but you control it the same as with any other category. I don’t think this has changed, though of course we have updated Spring of late.

But until the webapp is started, you’re logging through whatever Tomcat provides because the webapp’s bridge to SLF4J (and on to logback) isn’t in place yet. So possibly there’s something managing JCL logging and forcing it to the console.

With Jetty, you can’t control this output unless you manually add the jcl-over-slf4j jar into the Jetty lib folder. But without it, my experience is you get no output, not DEBUG output. I can check that.

( https://shibboleth.atlassian.net/browse/IDP-1945#add-comment?atlOrigin=eyJpIjoiZGExYWRmNThiMzdiNGYxODg5ZWZjYzkwMjNkYTVmMWYiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/IDP-1945#add-comment?atlOrigin=eyJpIjoiZGExYWRmNThiMzdiNGYxODg5ZWZjYzkwMjNkYTVmMWYiLCJwIjoiaiJ9 )

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/582d498b/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-eef8aa60-8b14-44b3-b7d8-3e40fd253649
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220429/582d498b/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-c1f15e62-ef05-4584-9115-f4c71b0a4550
Type: image/png
Size: 425 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220429/582d498b/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-484b4fa7-9978-4510-a91c-24869b9a3b05
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220429/582d498b/attachment-0005.png>