Logging configuration completely ignored in Config.groovy when deployed as a war?

Question

When I run my application with run-app, logging seems to work correctly. When I deploy as a WAR in tomcat, all my logging configuration is ignored, and I only see

LOGLEVEL logmessage

Example:

INFO Hello world

What could possibly be causing this? I tried deleting tomcat's logging.properties, but that didn't seem to do anything.

duplicate? http://stackoverflow.com/questions/6792420/grails-no-logging-in-tomcat — Michael J. Lee, Jul 27 '11 at 18:54
I get logging, but the format is wrong. My initial thought is that something else could be overriding the log4j configuration, which is probably different than no-logging whatsoever. — Stefan Kendall, Jul 27 '11 at 19:13
What is your pattern set to in the relevant appender? The log4j closure of Config would be useful information. — chrislatimer, Jul 29 '11 at 13:25
I'm using the default Config.groovy and I see this behavior. — Stefan Kendall, Jul 29 '11 at 19:39

score 0 · Accepted Answer · answered Aug 16 '11 at 17:17

0

Even after wiping the logging entirely, I still see this in catalina.out, while my logs to a log file are written correctly. A plugin or library, likely, is screwing up my logging, but tracing it down at this point isn't worth it.

answered Aug 16 '11 at 17:17

Stefan Kendall

66,414
68
253
406

Logging configuration completely ignored in Config.groovy when deployed as a war?

1 Answers1