Gregory Engel wrote:
Dave wrote:
On Thu, Apr 24, 2008 at 12:17 PM, Skid <[EMAIL PROTECTED]> wrote:
Well that doesn't seem to work either.
I tried it.
It's odd. If I run from an IDE typically I can see all the System.out's
in the console area at the bottom. But if I run with roller deployed
all output ends at "INFO [STDOUT] Roller Weblogger: Successfully loaded
custom properties file from classpath"
Doesn't matter if I have configured log4j in roller-custom.properties or
not. No more console messages and no logging.
Yeah, using log4j in an app server environment has always been quirky.
I get this same problem running Roller on JBoss. Have been meaning
to research a solution forever and just haven't found time. But in the
meantime, note that logging does still happen. It's just that the
Roller config somehow supercedes the container config.
Look in $JBOSS_HOME/server/default/logs for a file named roller.log.
You *might* have to pre-create that directory and/or even touch the file
before starting JBoss, but it should work. Everything that gets logged
after the "INFO [STDOUT] Roller Weblogger: Successfully loaded
> custom properties file from classpath" line will go into roller.log
instead of JBoss' server.log.
TTYL,
--
Phillip Rhodes
Chief Architect - OpenQabal
https://openqabal.dev.java.net
LinkedIn: http://www.linkedin.com/in/philliprhodes
