[
https://issues.apache.org/jira/browse/GERONIMO-5565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132638#comment-13132638
]
Baris Sener commented on GERONIMO-5565:
---------------------------------------
Then can't we do something like:
log4j.appender.CONSOLE=org.apache.log4j.RollingFileAppender
log4j.appender.CONSOLE.Threshold=TRACE
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern=%d{ISO8601} %-5p [%c{1}] %m%n
log4j.appender.CONSOLE.append=true
log4j.appender.CONSOLE.file=${org.apache.geronimo.server.dir}/var/log/geronimo.out
log4j.appender.CONSOLE.bufferedIO=false
log4j.appender.CONSOLE.maxBackupIndex=3
log4j.appender.CONSOLE.maxFileSize=10MB
> geronimo.out can grow unbounded
> -------------------------------
>
> Key: GERONIMO-5565
> URL: https://issues.apache.org/jira/browse/GERONIMO-5565
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: commands, Logging
> Affects Versions: 2.1.6, 2.2, 3.0
> Reporter: Kevan Miller
> Fix For: 3.0
>
>
> By default, Geronimo will log WARN (and above) messages to STDOUT. When you
> start Geronimo in the background, this means that any WARN, ERROR, etc
> messages will be sent to the file geronimo.out. There is no guard for this
> file. So, it will grow unbounded. Unlike log files, which are configured with
> a maximum size.
> We need procedures and mechanisms to prevent the geronimo.out file from
> growing too large.
--
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
