OK, what I found out until now:
- All test classes of the Camel LevelDB component contain only 1 Test
- The POM of the component contains a surefire config
"pertest"
=> what means the same as "always"
=> what means "fork for each test-class" (yes, the term "pertest" is very
confusing)
Therefo
Hi Camel users
I ran into another problem with the LevelDB aggregator persistence. The
error I get is "Error opening LevelDB with file [path to persistentFileName]".
The cause of it is "LOCK: already held by process".
This happens when I run multiple route tests using CamelSpringTestSupport.
The
