[
https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187306#comment-15187306
]
Remko Popma commented on LOG4J2-1116:
-------------------------------------
Interesting idea. Reflection hacking, so it may fail etc, but then we are no
worse off then we were before... Yes, I can see the value of that. We'd need
all ThreadLocals we might have initialized in Log4j, which is a bit of a pain
to manage manually, but that can be done. We'd also need all Threads for which
a ThreadLocal has been initialized. That can be done in a utility collection to
which we add the current thread every time we call {{ThreadLocal.set(value)}}.
Nice idea, Matt!
> upgrade to log4j2 causes too frequent minor gc
> ----------------------------------------------
>
> Key: LOG4J2-1116
> URL: https://issues.apache.org/jira/browse/LOG4J2-1116
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.3
> Environment: jdk1.6
> slf4j 1.7.9
> log4j2.3
> Reporter: Mingjiang Shi
> Priority: Critical
>
> We used slf4j+log1.2 in our spring web application. Due to the log4j1.0
> performance issue, we upgrade it to log4j2. When it goes to production, it
> experienced very frequent minor gc (once per second) even though the eden
> area is not full. For example, the eden area just occupied 10%, the minor gc
> also happens. The issue disappears when rolling back to log4j1.2.
> Can anyone show some hints on diagnose this issue? Thanks!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
