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 individual tests run fine, if they run in the same test-run, the first
succeeds and the rest fails with the error above.
Since the Camel context is restarted per test, I also remove the whole
directory with the levelDB file in the @Before method of my test-classes,
so that the DB is "blank" for every test method.
Is this a wrong behaviour for the tests? What is the best practice to have
a new LevelDB for every test case.
Thanks for any help
Stephan
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 individual tests run fine, if they run in the same test-run, the first
succeeds and the rest fails with the error above.
Since the Camel context is restarted per test, I also remove the whole
directory with the levelDB file in the @Before method of my test-classes,
so that the DB is "blank" for every test method.
Is this a wrong behaviour for the tests? What is the best practice to have
a new LevelDB for every test case.
Thanks for any help
Stephan