Hello hsqldb devs! I'm trying to use hsqldb 1.7.3.1 on my Gentoo GNU/Linux box. While I've already solved most of the problems I've encountered, there seems to be the trouble with running hsqldb in Server mode.
After adding /etc/init.d/hsqldb file to the required runlevels, all is well when I start and shutdown the service. The same is for starting and shutting down (or restaring) the machine. However, when I try to use additional databases apart from the default "//localhost" and/or "test", the service doesn't seem to stop cleanly. I've already described the problem in Gentoo Bugzilla and I'm working on the fix. See: http://bugs.gentoo.org/show_bug.cgi?id=111963 http://bugs.gentoo.org/show_bug.cgi?id=111963#c3 DETAILS What I want to do is to specify additional database(s) in the 'server.properties' file, like: ----- server.database.0=file:/var/lib/hsqldb/db1 server.urlid.0=localhost server.database.1=file:/var/lib/hsqldb/jdo/jdo server.dbname.1=jdo ----- Then after starting the hsqldb, the /var/lib/hsqldb/jdo dir is created and I can see in /var/log/hsqldb.log: [EMAIL PROTECTED]: Database [index=0, id=0, db=file:/var/lib/hsqldb/db1, alias=] opened sucessfully in 408 ms. [EMAIL PROTECTED]: Database [index=1, id=1, db=file:/var/lib/hsqldb/jdo/jdo, alias=jdo] opened sucessfully in 44 ms. So far, so good. But trying to stop the server proves to be unsuccessful. The 'hsqldb' script only tries to shutdown the 'localhost' instance (which works), but after this the org.hsqldb.Server is still running. So the script prints: "WARNING: hsqldb is still running!" >From what I discovered, this is caused by the fact that now there is an additional database, 'jdo'. Moreover, even after stopping the 'localhost' instance I can still connect to the 'jdo' database using org.hsqldb.util.DatabaseManager. So in order to stop the server cleanly I have to: 1) Add the 'jdo' database in 'sqltool.rc' file, like: ----- urlid localhost url jdbc:hsqldb:hsql://localhost username sa password urlid jdo url jdbc:hsqldb:hsql://localhost/jdo username sa password ----- 2) Stop the 'jdo' database by calling SqlTool directly: # java org.hsqldb.util.SqlTool --noinput --sql 'shutdown ;' \ --rcfile /var/lib/hsqldb/sqltool.rc jdo 3) Stop the service in a normal way: # /etc/init.d/hsqldb stop I want to ask if this is a misconfiguration problem on my side or the problem is of a bigger nature? What I would like to know is whether this is a known issue and get a hint how to deal with this. Note: I can't tell if this also applies to 1.8 release, because I was unable to install that version on my box (it doesn't exist in Gentoo repositories yet). And after trying to install 1.8.0.2 by hand it didn't start the server at all (requires further investigation), so I concentrated on 1.7.3.1 exclusively. Best regards, Wiktor Wandachowicz Registered Linux user #390131 (http://counter.li.org) ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ hsqldb-developers mailing list hsqldb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
