Uploaded image for project: 'Geronimo'
  1. Geronimo
  2. GERONIMO-607

Logging configuration is unnecessarily processed twice at startup

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • 1.0-M4
    • None
    • None

    Description

      The following currently occurs when Geronimo is started:

      1. Geronimo bootstraps logging to the console as part of the static initialisation in the Daemon class.

      2. The Log4j service GBean org.apache.geronimo.system.logging.log4j.Log4jService's 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 Log4jService causes the logging to be reconfigured (log file is closed and reopened) even though the logging configuration wasn't changed:

      if (lastChanged < lastModified)

      { lastChanged = lastModified; reconfigure(); }

      Attachments

        1. Log4jService_patch.txt
          2 kB
          John Sisson

        Activity

          People

            gianny Gianny Damour
            johnrsisson John Sisson
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: