Log4j 2
  1. Log4j 2
  2. LOG4J2-329

StatusLogger creates many objects with no way to limit them

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0-beta8
    • Fix Version/s: 2.0-beta9
    • Component/s: API
    • Labels:
      None

      Description

      StatusLogger creates StatusData objects and adds them to a queue. The user has no way to limit those and under certain circumstances a lot of objects will be created and deleted.

        Issue Links

          Activity

          Hide
          Remko Popma added a comment -

          The work to add configuration elements/attributes for system properties is tracked in LOG4J2-321. I intend to start on this soon. Next week I'll be traveling but the week after that I hope to be able to get this (and a few others) done.

          Show
          Remko Popma added a comment - The work to add configuration elements/attributes for system properties is tracked in LOG4J2-321 . I intend to start on this soon. Next week I'll be traveling but the week after that I hope to be able to get this (and a few others) done.
          Hide
          Gary Gregory added a comment -

          OK, great, thank you for the explanation.

          Show
          Gary Gregory added a comment - OK, great, thank you for the explanation.
          Hide
          Ralph Goers added a comment - - edited

          StatusLogger initializes before any configuration is even read so it has to default from a system property. You specify the logging level of the ConsoleListener by specifying it on the configuration element, which is documented.

          Yes, we need a section just on the system properties and also that they can be loaded from a file.

          Show
          Ralph Goers added a comment - - edited StatusLogger initializes before any configuration is even read so it has to default from a system property. You specify the logging level of the ConsoleListener by specifying it on the configuration element, which is documented. Yes, we need a section just on the system properties and also that they can be loaded from a file.
          Hide
          Gary Gregory added a comment -

          This needs to be documented.

          It seems we have more and more secret system properties...

          Why is this not configurable from the normal configuration file, or is it?

          IMO, the system properties should only be used to override the configuration file, in case you cannot control it, or you to try a one-off tweak.

          Show
          Gary Gregory added a comment - This needs to be documented. It seems we have more and more secret system properties... Why is this not configurable from the normal configuration file, or is it? IMO, the system properties should only be used to override the configuration file, in case you cannot control it, or you to try a one-off tweak.
          Hide
          Ralph Goers added a comment -

          The user may now control the default level of the StatusLogger by setting the log4j2.StatusLogger.level system property to the appropriate level. As listeners are added the StatusLogger level will change as required to include their level.

          Show
          Ralph Goers added a comment - The user may now control the default level of the StatusLogger by setting the log4j2.StatusLogger.level system property to the appropriate level. As listeners are added the StatusLogger level will change as required to include their level.

            People

            • Assignee:
              Unassigned
              Reporter:
              Ralph Goers
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development