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 "Gary Gregory (JIRA)" <ji...@apache.org> on 2014/02/09 03:53:19 UTC

[jira] [Created] (LOG4J2-532) Resource leak in Flume appender when it cannot create a BerkeleyDB db.

Gary Gregory created LOG4J2-532:
-----------------------------------

             Summary: Resource leak in Flume appender when it cannot create a BerkeleyDB db.
                 Key: LOG4J2-532
                 URL: https://issues.apache.org/jira/browse/LOG4J2-532
             Project: Log4j 2
          Issue Type: Bug
          Components: Appenders
    Affects Versions: 2.0-beta9
         Environment: Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 11:22:22-0400)
Maven home: C:\Java\apache-maven-3.1.1\bin\..
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_51\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
            Reporter: Gary Gregory
            Assignee: Gary Gregory
             Fix For: 2.0-rc1


There is a rare but possible resource leak of a BerkeleyDB environment object in the Flume appender when it cannot create a BerkeleyDB db.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

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