Uploaded image for project: 'Mule'
  1. Mule
  2. MULE-4137

Log4jNotificationLoggerAgent is useless

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.1.2
    • Fix Version/s: 3.0.0-RC3
    • Component/s: Core: Agents
    • Labels:
      None
    • User impact:
      Low
    • Similar Issues:

      Description

      I don't see how its private attribute eventLogger could be something else than null with the big chunk of code commented out in doInitialise.

      Because it is null, logEvent does nothing.

      Could it be possible to uncomment these lines, until the OSGi/PAX quagmire is sorted out:

      else

      { /* ... */ eventLogger = Logger.getLogger(logName); /* ... */ }

      so at least a logger will be active?

      PS. That would also call for a review of getDescription, which does not acknowledge the fact a non-blank logName is an interesting configuration value.

        Attachments

          Activity

            People

            • Assignee:
              davidd David Dossot
              Reporter:
              ddossot David Dossot
            • Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                14/Sep/10