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 "David Koch (JIRA)" <ji...@apache.org> on 2013/10/23 17:43:42 UTC

[jira] [Commented] (LOG4J2-282) log4j2 jvm flag for debug information

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

David Koch commented on LOG4J2-282:
-----------------------------------

Using 2.0-beta9, I can't get this to work using system properties {{-Dlog4j.Log4jDefaultStatusLevel=DEBUG}} has no effect.

> log4j2 jvm flag for debug information
> -------------------------------------
>
>                 Key: LOG4J2-282
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-282
>             Project: Log4j 2
>          Issue Type: Wish
>          Components: Configurators
>    Affects Versions: 2.0-beta7
>            Reporter: Christian Lutz
>            Priority: Minor
>             Fix For: 2.0-beta8
>
>
> In log4j 1.2 it was possible to add -Dlog4j.debug (and some other flags) to the command line jvm call. 
> Example: java -Dlog4j.debug -jar abc.jar
> This is very helpfull for analysing any kind of errors. Is there any equivialent within log4j2?



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org