geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Sisson (JIRA)" <>
Subject [jira] Updated: (GERONIMO-607) Logging configuration is unnecessarily processed twice at startup
Date Fri, 11 Mar 2005 06:57:53 GMT
     [ ]

John Sisson updated GERONIMO-607:

    Attachment: Log4jService_patch.txt

Patch attached for review.

> Logging configuration is unnecessarily processed twice at startup
> -----------------------------------------------------------------
>          Key: GERONIMO-607
>          URL:
>      Project: Geronimo
>         Type: Bug
>     Reporter: John Sisson
>     Priority: Minor
>  Attachments: Log4jService_patch.txt
> The following currently occurs when Geronimo is started:
> 1. Geronimo bootstraps logging to console as part of the static initialisation in the
Daemon class.
> 2. The Log4j service GBean's Log4jService.doStart() is called, which in turn calls Log4jService.reconfigure()
which in turn causes Log4j's to be configured, therefore opening geronimo.log.  Log4jService.doStart()
also starts a timer for monitoring modifications to the log configuration file.
> 3. The timer pops for the first time and since the "lastchanged" variable is -1 the statement
at line 411 of org.apache.geronimo.system.logging.log4j.Log4jService causes the logging to
be reconfigured (even though the logging configuration wasn't changed):
>                 if (lastChanged < lastModified) {
>                     lastChanged = lastModified;
>                     reconfigure();
>                 }

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message