[
https://issues.apache.org/jira/browse/OFBIZ-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14100574#comment-14100574
]
Jacopo Cappellato edited comment on OFBIZ-5287 at 8/18/14 12:17 PM:
--------------------------------------------------------------------
[~adri...@hlmksw.com]: with loggers you can fine tune what is logged into
appenders; I didn't remove the loggers we have currently I am just using less
appenders; but we can definitely modify this in the next few days if we prefer,
it is just a configuration change.
Stack traces are still there as before of course; however the java file name
and line that created the logging is no more available. But again, this is a
configuration change that can be enabled in local environments.
was (Author: jacopoc):
[~adri...@hlmksw.com]: with loggers you can fine tune what is logged into
appenders; I didn't remove the loggers we have currently I am just using less
appenders; but we can definitely modify this in the next few days if we prefer,
it is just a configuration change.
Stack traces are still there as before of course; however the java file name
and line that created the logging is no more available.
> 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
> Fix For: Upcoming Branch
>
> 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)
