Stream: implementers
Topic: hapi-fhir-jpaserver-example
Patrick Werner (Mar 31 2016 at 12:58):
@James Agnew
i just upgraded our HAPI JPA Server to 1.5 Snapshot. If i redeploy the server i always get: "Another instance of Derby may have already booted the database /var/lib/tomcat7/jpadb/jpaserver_derby_files." This wasn't the case some versions ago.
Am i doing something wrong? How is upgrading supposed to work?
James Agnew (Mar 31 2016 at 13:50):
Hi Patrick, that's doesn't sound to me like a version specific thing. I'd assume it's either that another instance still running or possibly a non-clean shutdown.
You could try deleting the .lck files from the Derby directory to force it to start.. That said, HAPI FHIR 1.5 has a bunch of database column and index changes/improvements in it. Derby is kind of a pain to migrate databses in, so it might be easier to just wipe the whole directory when you upgrade to 1.5 and repopulate the Derby DB.
Last updated: Apr 12 2022 at 19:14 UTC
