▪ Java does not behave consistently if something fails outside the VM context (for example, inside a native method call). If something should assert (or even crash) in the solidDB server native code, Java either exits abnormally or hangs up completely. In the latter case, you might have to kill the dangling Java process manually.

▪ To minimize memory consumption, drop all allocated statements explicitly; all allocated JDBC statement objects must be explicitly freed by calling the close() method. Freeing objects is important especially if your setup uses Transparent Connectivity (TC).