Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Mon, 25 Jul 2016 12:34:20 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.12992257.1469449941000.122897.1469450060444@Atlassian.JIRA>
In-Reply-To: <JIRA.12992257.1469449941000@Atlassian.JIRA>
References: <JIRA.12992257.1469449941000@Atlassian.JIRA> <JIRA.12992257.1469449941013@arcas>
Subject: [jira] [Commented] (AMQ-6372) KahaDB reader pool not releasing
 unused open files till deletion - too many open files
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 25 Jul 2016 12:34:22 -0000


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

ASF subversion and git services commented on AMQ-6372:
------------------------------------------------------

Commit d427952b19f1763d5128d8a6c145d61dcefd79d9 in activemq's branch refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=d427952 ]

AMQ-6372 - fix up accessor pool cleanupUnused and use the minimum number of open files for recovery


> KahaDB reader pool not releasing unused open files till deletion - too many open files
> --------------------------------------------------------------------------------------
>
>                 Key: AMQ-6372
>                 URL: https://issues.apache.org/jira/browse/AMQ-6372
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: KahaDB
>    Affects Versions: 5.13.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.14.0
>
>
> Leading to: 
> {code}java.io.FileNotFoundException: .../kahadb/db-2300.log (Too many open files){code}
> Kahadb has an accessor pool of random access files and a periodic cleanup. However the cleanup does not work as expected.
> Only on journal gc does the pool get purged.
> This issue can arise with very large amounts of journal files that are paging and on recovery when the entire journal needs to be replayed.
> In essence, currently there needs to be fd per journal data file.
> The workaround is to increase the nofiles (max open files) for the broker process.


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