You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2013/08/02 23:35:50 UTC

[jira] [Commented] (LOG4J2-329) StatusLogger creates many objects with no way to limit them

    [ https://issues.apache.org/jira/browse/LOG4J2-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728152#comment-13728152 ] 

Gary Gregory commented on LOG4J2-329:
-------------------------------------

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.
                
> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org