Ubuntu
hsqldb package

  1. Bug #1153856
  2. Comment #2

Comment 2 for bug 1153856

Revision history for this message
John Agombar (78luphr0rnk2nuqimstywepozxn9kl19tqh0tx66b5dki1xxsh5mkz9gl21a5rlwfnr8jn6ln0m3jxne2k9x1ohg85w3jabxlrqbgszpjpwcmvkbcvq9spp6z3w5j1m33k06tlsfszeuscyt241ha-launchpad-a811i2i3ytqlsztthjth0svbccw8inm65tmkqp9sarr553jq53in4xm1m8wn3o4rlwaer06ogwvqwv9mrqoku2x334n7di44o65qze67n1wneepmidnuwnde1rqcbpgdf70gtqq2x9thj5tlcsac1) wrote :

After some more investigation I found that if I did
 sudo /etc/init.d/hsqldb-server stop
before shutting down then the shutdown would complete fine.

Yet more investigation revealed that editing /etc/hsqldb.conf and setting
HSQLDB_OWNER=my_id
and changing the owner and group of the database directory and files in
/var/lib/hsqldb
to my_id allowed the shutdown to complete successfully without the forced stop of the server above.

Hope that these might help....