[CAMEL-13443] Camel Blueprint JUnit Test keeps Filelock after Test

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.23.1
• Fix Version/s: 3.8.0
• Component/s: camel-blueprint, camel-test
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Florian Wermelskirchen
• Created: 23/Apr/19 08:37
• Updated: 21/Dec/20 13:36
• Resolved: 21/Dec/20 13:36

Description

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.