[
https://issues.apache.org/jira/browse/LOG4J2-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683142#comment-13683142
]
Christian Lutz edited comment on LOG4J2-282 at 6/14/13 6:31 AM:
----------------------------------------------------------------
I saw this one. But this option is only working if the log4j2.xml file is used.
In the described jvm way will always work.
was (Author: christianl):
I saw this one. But this option is only working if the log4j2.xml file is
used. In the described jvm way, it will always work.
> 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
>
> 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 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-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
