geronimo-dev mailing list archives

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


Kevan Miller commented on GERONIMO-5565:

Conceptually, yes (I didn't check the specifics of your config). However, this won't capture
STDOUT/STDERR (e.g. callers of System.out.println())

Ideally, we'd rebind System.out and System.err to a PrintStream that "logs" output to the
rolling "console" file.

This would be a nice feature to have.
> geronimo.out can grow unbounded
> -------------------------------
>                 Key: GERONIMO-5565
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message