You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Peter Bacsko (JIRA)" <ji...@apache.org> on 2018/05/30 13:07:00 UTC

[jira] [Updated] (OOZIE-3268) Derby DB is used in some tests which might lead to "Too many open files"

     [ https://issues.apache.org/jira/browse/OOZIE-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Bacsko updated OOZIE-3268:
--------------------------------
    Summary: Derby DB is used in some tests which might lead to "Too many open files"  (was: TestCoordELExtensions should restore the property "oozie.test.config.file")

> Derby DB is used in some tests which might lead to "Too many open files"
> ------------------------------------------------------------------------
>
>                 Key: OOZIE-3268
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3268
>             Project: Oozie
>          Issue Type: Sub-task
>            Reporter: Peter Bacsko
>            Assignee: Peter Bacsko
>            Priority: Major
>
> The following {{setUp()}} method can cause serious test problems depending the order of test execution:
> {noformat}
>    @Override
>     protected void setUp() throws Exception {
>         setSystemProperty("oozie.test.config.file", new File(OOZIE_SRC_DIR,
>                 "core/src/test/resources/oozie-site-coordel.xml").getAbsolutePath());
>         super.setUp();
>         services = new Services();
>         setClassesToBeExcluded(services.getConf(), excludedServices);
>         services.init();
>     }
> {noformat}
> The problem is, this causes Oozie to switch to Derby from HSQLDB. However, before every testcase, the previous instance of Derby is not closed, leading to excessive number of open files. After a certain point, all tests fail with "Too many files open" exception.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)