Increasing logging in IdP 2.3.6

[Brent Putman]

On 4/24/13 1:25 PM, Cantor, Scott wrote:
> Never really been sure whether it reloads or not. Says it does, but I've
> seen cases where it doesn't.

I've never paid much attention to the reloading behavior either.  I just did some quick testing on
my test IdP (currently 2.3.8, Jetty 7, RHEL 5.x) and it seems to reload ok for me. 

I did note an error in the wiki page, it says reload every 5 minutes but is actually 10 minutes by
default according to internal.xml.

It's possible there is a bug in an earlier version, but I don't see anything in Jira.

To the OP: If you want to try and get some diagnostic data about whether the reload is being
attempted, you can do one or both of the following:

1) Add a DEBUG level logger for category org.opensaml.util.resource.ResourceChangeWatcher.  This
will log whenever a change event fires, giving you a hint that reloading is happening, or at least
being attempted.

2) Add debug="true" to the top-level <configuration> element of logging.xml.  This will spit out
some diagnostic output from logback itself to stdout or stderr when it loads a configuration, so
check your container logs for those.


One possibility that comes to mind is that if your logging.xml is malformed, has syntax or semantic
errors, etc, then logback won't be able to reload it.  There might be some indication of this in
your container logs, or wherever stdout/stderr goes.

--Brent