[
https://issues.apache.org/jira/browse/LOG4J2-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728155#comment-13728155
]
Ralph Goers edited comment on LOG4J2-329 at 8/2/13 9:39 PM:
------------------------------------------------------------
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.
was (Author: [email protected]):
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
document.
Yes, we need a section just on the system properties and also that they can be
loaded from a file.
> StatusLogger creates many objects with no way to limit them
> -----------------------------------------------------------
>
> Key: LOG4J2-329
> URL: https://issues.apache.org/jira/browse/LOG4J2-329
> Project: Log4j 2
> Issue Type: Improvement
> Components: API
> Affects Versions: 2.0-beta8
> Reporter: Ralph Goers
> Fix For: 2.0-beta9
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
