I should add: ... if any hsqldb connections are left open at completion of main(). If you close all your connections, then the program exits when main() completes.
But note that this means that an uncaught exception may not exit your program, if it throws past connection closing. (this is all with a local file url, not the remote case). I don't know how many threads hsqldb starts, nor what they do, nor whether this is deliberate. > i note that hsqldb is currently not using Thread.setDaemon(true) on its threads. > That means that they behave like user threads, and will prevent a program from > exiting, even after the main thread completes. _______________________________________________ hsqldb-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hsqldb-developers