Lets get this out for discussion. AFAIK, currently Jetty does not come
with these things automatically enabled (correct me if I am wrong but
did not notice a config for Jetty). Deployer and client do, but I do
not see Jetty.
Therefore, I think we need to be consistent...if we make this
Jetty logs are directed to jetty__mm_dd.log using
JettyRequestLog gbean. When we decide to provide the
facility to replace Jetty with Tomcat, the Logger
gbean in tomcat can be used to replace JettyRequestLog
in j2ee-server-plan.xml.
--- Jeff Genender [EMAIL PROTECTED] wrote:
Lets get this out
Jeff,
Yes it does. By default the Digester should be
turned off and a comment out line to turn it on. As an
application developer, I would like my tomcat output
to be free of gbeans. I also think we should have a
separate tomcat-log4j.properties file just like
jetty, deployer and client. I
Submit away! I can use the help.
Jeff
anita kulshreshtha wrote:
Jeff,
Yes it does. By default the Digester should be
turned off and a comment out line to turn it on. As an
application developer, I would like my tomcat output
to be free of gbeans. I also think we should have a
separate
I find it convenient to log only INFO level logs from
tomcat to geronimo.log and DEBUG level logs to a
separate file. Digester produces too much output and
it is hard to sift through the logs.
Thanks
Anita
--- Jeff Genender [EMAIL PROTECTED] wrote:
Anita,
Can you be more specific in your
Anita,
I believe a log4j configuration should allow you to do what you want.
You should be able to control certain packages (i.e. Digester) to go to
its own log file and you should be able to set the level of debugging.
Jeff
anita kulshreshtha wrote:
I find it convenient to log only INFO
Anita,
Can you be more specific in your question? Are you saying you want a Tomcat
log to go to another log file?
Jeff
-Original Message-
From: anita kulshreshtha [mailto:[EMAIL PROTECTED]
Sent: Monday, May 23, 2005 3:07 AM
To: dev@geronimo.apache.org
Subject: Logging in Tomcat
Jeff
