logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-887) There is a memory leak and Eclipse Memory analysis has flagged the instance “com.sleepycat.je.tx.SyncedLockManager
Date Sun, 12 Apr 2015 19:28:12 GMT

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

Ralph Goers commented on LOG4J2-887:
------------------------------------

Gary, it is unlikely that will make any difference. 

Avinash works for one of my previous employers. My understanding is that after I left Avinash
modified the FlumeAppender and FlumePerstientManager as described in LOG4J2-714. They asked
me to review the patch, which I did, and I told them I could not apply it as provided. I have
never had the time to work up a proper patch for that issue, although I do intend to.  However,
my understanding is that they are using that code and that is what is causing this problem.
 As I noted above, FlumePersistentManager only creates a single Environment (it is declared
to be final), so I just don't see how the existing code could cause this problem.  Notice
that in the patch provided in LOG4J2-714 the Environment is declared as volatile.

> There is a  memory leak and Eclipse Memory analysis has flagged the instance “com.sleepycat.je.tx.SyncedLockManager
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: LOG4J2-887
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-887
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Flume Appender
>    Affects Versions: 2.0-rc1
>         Environment: PRODUCTION, Red Hat Linux 5
>            Reporter: Avinash Dhananjay
>            Priority: Critical
>
> There is a  memory leak and Eclipse Memory analysis has flagged the instance “com.sleepycat.je.tx.SyncedLockManager.
> Also, there are 308 ERRORs in thelog file, ERROR Caused by java.util.concurrent.RejectedExecutionException:
null.  Is one of the thread pools being exhausted?
> One instance of "com.sleepycat.je.txn.SyncedLockManager" loaded by"org.jboss.classloader.spi.base.BaseClassLoader
@ 0x732e868e8" occupies33,555,808 (12.79%) bytes. The memory is accumulated in one instance
of"java.util.HashMap$Entry[]" loaded by "<system class loader>".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message