4.2 upgrade issues

[Cantor, Scott]

On 5/4/22, 1:20 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:

>    >    I mean on IdP startup to the container log (catalina.out) in our case. We see all values logged each time. I
>    > don't think we've customised the logging levels in this case. I can check tomorrow.
>
>   Somebody else already reported this supposedly happening on Tomcat, but it doesn't happen on Jetty, so 
> Tomcat is being its usual self.

It looks like it is in fact an IdP bug sort of, in that we didn't know logback actually defaults to DEBUG (which seems odd, but whatever). Jetty with logback tends to spin thatv up early enough with a dedicated logging config but Tomcat without logback won't so it defaults. We had a file we didn't think we wanted sitting in classpath:/logback.xml that was "accidentally" defaulting logging to WARN so that changed things.

We may restore that given everything, but it's filed and we'll address it eventually some way. In the meantime, one workaround is just setting -Dlogback.configurationFile to something up front yourself.

-- Scott