Hi
I’m trying to deploy Axon Server docker image on https://sliplane.io/ platform.
This platform allows for attaching persistent volumes to given docker container deployment.
When I deploy for the first time the Axon Server container it runs fine. But when I redeploy it I’m getting following error:
Database may be already in use: "/axonserver/data/axonserver-configdb.mv.db". Possible solutions: close all other connection(s); use the server mode [90020-232]
...
...
Caused by: org.h2.mvstore.MVStoreException: The file is locked: /axonserver/data/axonserver-configdb.mv.db [2.3.232/7]
My guess is that: on redeploy there’s no proper shut down of the old axon server docker container process and somehow lock is not removed. I do not see any *.lock files left in the persistent volume, but I assume there’s some different lock mechanism.
What’s bizzare, even though I get the error in logs, when I call the /actuator/health endpoint it returns 200 with information on db status: “UP”.
Therfore, my questions:
- Do you know what is the factual problem here? Is factually it related with unreleased lock?
- How to solve this issue? Is there some JAVA_OPTS that I can specify to remove the H2 from putting locks? Or some other config property for axon server that may resolve it?