Thanks i'll give it a shot. Is there any logging in derby that i can enable into regarding this?
On Sat, Feb 6, 2021 at 7:08 PM Rick Hillegas <rick.hille...@gmail.com> wrote: > The usual cause for this behavior is that the application was brought > down ungracefully, say via a control-c or by killing the window where it > was running. The engine then needs to reconstruct the state of the > database by replaying many recovery logs. To gracefully exit Derby, you > need to explicitly shutdown Derby as described here: > https://db.apache.org/derby/docs/10.15/devguide/tdevdvlp20349.html > > On 2/6/21 3:39 PM, Alex O'Ree wrote: > > Sometimes when my app starts, it can take several minutes to initialize > the > > database. Is there a way to find out whats going on? There isn't much log > > output. I have overridden derby.stream.error.method but other than the > the > > startup message, I don't have much to go on. > > > > Is there perhaps a startup database file check or something? > > > >
