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, 25 Jan 2015 23:21:34 GMT

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

Ralph Goers commented on LOG4J2-887:

Is there a log file or anything to help diagnose this problem?  Although I am sure this is
related to the FlumeAppender, nothing has been provlded to indicate that the problem is in
the Appender and not in BerkeleyDB.

Also, a web search yields https://community.oracle.com/thread/3623927, which looks to be the
exact text of this problem so I assume you asked Oracle first. Their response indicates that
new environments are being created without the previous environment being closed. Since the
environment in the FlumePersistentManager and the environment is closed when the Manager is
stopped I am having a hard time understanding how the FlumePersistentManager could cause this.

Are you using a version of the changes you proposed for LOG4J2-714? If so, that could likely
cause this issue.

> 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: Blocker
> 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

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

View raw message