Re: Fortress debug output and default stack traces.

Leif Mortenson wrote:
> I have been trying to get back into Fortress by using it on a new
> project. The current version is kicking out a lot of stack traces
> at the debug level of the "fortress" log channel. I have included
> them below. None of these are actual problems, so I was wondering
> if there is a reason why they are being displayed.
> 
> The obvious fix is to disable log output, presto problem goes away.
> But the problem there is that all of the components are assigned
> loggers which are child loggers of the "fortress" logger. If I want
> to have debug output enabled for them, but disabled for fortress,
> then I have to configure them each individually in the xlog config
> file.
> 
> In general showing stack traces for things other than an actually
> problem seems like a good thing to avoid. When I first saw them, I
> assumed that something was broken.

That was a result of a change I made to ContextManager when I was
tracking down an initialization bug--there was an NPE thrown
somewhere.  We can disable the logging for those particular points
without problems.