[
https://issues.apache.org/jira/browse/GERONIMO-5864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253172#comment-13253172
]
Saphen Qiu commented on GERONIMO-5864:
--------------------------------------
After set the log level of
"log4j.logger.org.apache.catalina.core.ContainerBase" from WARN to INFO I can
not see additional logs when server starts.
When running a sample with such ServletContext.log() method, the ServletContext
log will be logged in geronimo.log file.
At the meanwhile, I checked the geronimo svn site, but can not find the
revision of why the log level be changed to WARN. So I don't know why most of
the log4j.logger.* level is set to WARN by default, maybe it is used to get
best performance.
According to this defect, shall we change the default value to INFO or just
change document to tell user if they want to see the ServletContext log they
have to set the log level of
"log4j.logger.org.apache.catalina.core.ContainerBase" to INFO by manually?
> ServletContext.log doesn't log
> ------------------------------
>
> Key: GERONIMO-5864
> URL: https://issues.apache.org/jira/browse/GERONIMO-5864
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 3.0
> Reporter: Kevan Miller
> Assignee: Saphen Qiu
> Fix For: 3.0
>
>
> ServletContext.log() calls aren't logged anywhere (as far as i can tell).
> This is on a tomcat server. I didn't test a jetty assembly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
