You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2019/10/01 08:44:00 UTC

[jira] [Commented] (CAMEL-13443) Camel Blueprint JUnit Test keeps Filelock after Test

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

Claus Ibsen commented on CAMEL-13443:
-------------------------------------

Yeah it may be a bit more slower now. Anyone able to dive in and try to find out would be appreciated.

> 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)