[jira] [Commented] (OFBIZ-5287) Migrating from Log4j 1.2.17 to log4j2

[Nicolas Malin (Jira)]

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

Adrian Crum commented on OFBIZ-5287:
------------------------------------

Jacopo,

Please don't remove the additional appenders. FOP logging is extremely verbose and it seriously impacts performance. It is a separate appender so it can be disabled.

Thank you for the detailed explanation, but I still don't understand what is being done with stack traces. Do we still have them when an exception is thrown?

I look forward to these changes. On my laptop I noticed that thousands of log messages are skipped because the logger can't keep up. That makes it hard to debug problems. I hope these changes fix that.

> Migrating from Log4j 1.2.17 to log4j2
> -------------------------------------
>
>                 Key: OFBIZ-5287
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5287
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: framework
>    Affects Versions: Trunk
>            Reporter: Jacques Le Roux
>            Assignee: Jacopo Cappellato
>            Priority: Minor
>         Attachments: log4j2.patch
>
>
> Mostly because of the introduction of  [LMAX Disruptor library|http://martinfowler.com/articles/lmax.html] in log4j 2, but not only, I want to upgrade log4j to [log4j 2|http://logging.apache.org/log4j/2.x/]
> [The migration does not seem too hard to do| http://logging.apache.org/log4j/2.x/manual/migration.html]. I found only usage of Appender when unloading containers and of course in
> Debug.java; Appender  and LoggerRepository  classes
> There is also [a easy to install bridge for SLF4J|https://loggapache.org/log4j/2.x/log4j-slf4j-impl/index.html]
> About LMAX Disruptor, [here is a brief introduction|http://stackoverflow.com/questions/6559308/how-does-lmaxs-disruptor-pattern-work],
> I discovered the usage of LMAX Disruptor in log4j2 [through this blog entry|http://www.grobmeier.de/log4j-2-performance-close-to-insane-20072013.html#.UepjvGTfxFo]

--
This message was sent by Atlassian JIRA
(v6.2#6252)