[
https://issues.apache.org/jira/browse/CAMEL-13443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252752#comment-17252752
]
Claus Ibsen commented on CAMEL-13443:
-------------------------------------
Okay so this is only per unit test that the open files are kept but will be
closed when the entire test suite is done. And as such if you run
camel-test-blueprint as test itself it may open 400 files to run all its tests.
> Camel Blueprint JUnit Test keeps Filelock after Test
> ----------------------------------------------------
>
> Key: CAMEL-13443
> URL: https://issues.apache.org/jira/browse/CAMEL-13443
> Project: Camel
> Issue Type: Bug
> Components: camel-blueprint, camel-test
> Affects Versions: 2.23.1
> Reporter: Florian Wermelskirchen
> Priority: Minor
>
> I use CamelBlueprintTestSupport for my JUnit Tests. CamelBlueprintTestSupport
> keeps FileLocks on jar Files in target/test-bundles. Due to this, my Tests
> fails on Jenkins, because of FileNotFoundException (too many open files). My
> current workaround is to Run every Test in a single JVM.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
