You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Avinash Dhananjay (JIRA)" <ji...@apache.org> on 2014/10/28 06:53:34 UTC

[jira] [Created] (LOG4J2-887) There is a memory leak and Eclipse Memory analysis has flagged the instance “com.sleepycat.je.tx.SyncedLockManager

Avinash Dhananjay created LOG4J2-887:
----------------------------------------

             Summary: 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
             Fix For: 2.1


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