geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GERONIMO-5565) geronimo.out can grow unbounded
Date Fri, 21 Oct 2011 08:14:32 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-5565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132504#comment-13132504
] 

Ivan commented on GERONIMO-5565:
--------------------------------

IMO, there is no way to do this, as it is done by the target OS. Other solution is that, change
the log level for CONSOLE in the var/log/server-log4j.properties or just comment it out, as
you still could see those outputs in the log files.
                
> 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

        

Mime
View raw message