When using SQL Explorer with Derby embedded driver closing all connection do not correctly shutdown Derby, the db.lck remains.
With the Database Development Perspective after closing the connection the db.clk disappears, wich is the right behavior.
The shutdown of Derby embedded is somehow special, you have to open a connection with the shutdown=true property.
Does anyone know about this problem ?
so long Torsten
Log in to post a comment.
When using SQL Explorer with Derby embedded driver closing all connection do not correctly shutdown Derby, the db.lck remains.
With the Database Development Perspective after closing the connection the db.clk disappears, wich is the right behavior.
The shutdown of Derby embedded is somehow special, you have to open a connection with the shutdown=true property.
Does anyone know about this problem ?
so long
Torsten