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/04/29 07:43: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=16828998#comment-16828998 ] 

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

Are you able to find out which files it has a lock on? I wonder if its the test bundle itself, or the karaf bundles or something. eg if the former its maybe something in camel we can fix, but the latter may be in apache felix/karaf etc.

> 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-test
>    Affects Versions: 2.23.1
>            Reporter: Florian Wermelskirchen
>            Priority: Major
>
> 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
(v7.6.3#76005)