I think this is related to the custom log4j bits on geronimo-kernel,
which most modules depend on. Modules that do not depend on geronimo-
kernel, like geronimo-util and geronimo-activation behave as I would
expect.
I'm gonna dig into it more, and will probably add a custom sys prop
to disable the kernel's logging bits, so that we can set that for
tests and thus get tests to use one log4j configuration. Though, I'd
imagine that it this is done in a static, that other projects that
use G components that also depend on geronimo-kernel will also end up
with some additional log4j configuration that is unwanted.
I don't want to start up a logging debate... so I think the optional
disable the kernels default should be fine to get test logging back
to normal, producing little console output and full debug to target/
test.log.
--jason
On Aug 30, 2006, at 4:50 PM, Dain Sundstrom wrote:
You should be able to turn on debugging, add a break point in the
logging code and see which test is causing the problem.
-dain
On Aug 30, 2006, at 4:31 PM, Jason Dillon wrote:
Looks like there is more going on which is causing tests to use
some additional configuration for tests...
Specifically, looks like something else is installing a
ConsoleAppender... as if I comment out the CONSOLE definition from
logging-config, then I still get console output.
I'm also seeing that something is setting the root logger's
level... as I've got the root configured to use DEBUG, but that
will not output DEBUG logs to the test.log as I would expect. I
have to explicitly configure org.apache.geronimo to use DEBUG, and
then I see the logs in test.log... but now with some rouge
ConsoleAppender it spits out a bunch of junk to the console.
Highly frustrating... :-(
--jason
On Aug 30, 2006, at 3:53 PM, Jason Dillon wrote:
This is fixed now... though it still spits out a few ERROR logs,
which I am hoping are expected from the test...
--jason
On Aug 30, 2006, at 3:49 PM, Jason Dillon wrote:
Um... looks like a few of these tests are explicitly enabling
DEBUG and installing a ConsoleAppender...
Logger.getRootLogger().addAppender(new ConsoleAppender(new
PatternLayout("%p [%t] %m %n")));
Logger.getRootLogger().setLevel(Level.DEBUG);
I'm not sure how they were quiet before m2 with code like above
in setUp().
--jason
On Aug 28, 2006, at 4:29 PM, Jason Dillon wrote:
Thats odd, because the default logging config is set to only
allow WARN and ERROR to go to console, not DEBUG.
Do these tests need to:
GeronimoLogging.initialize(GeronimoLogging.INFO);
Or something?
--jason
On Aug 28, 2006, at 10:14 AM, Dain Sundstrom wrote:
Not me. They were quiet before the m2 change but it looks
like logging got turned up.
-dain
On Aug 28, 2006, at 2:26 AM, Jason Dillon wrote:
These tests make way... way to much noise.
Anyone know how to make them shut up?
--jason
