DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15135>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15135 hsqldb block cannot close correctly Summary: hsqldb block cannot close correctly Product: Avalon Version: unspecified Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Critical Priority: Other Component: Apps AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hi. I tried to use hsqldb-block in Phoenix-4.0.2 I built hsql.sar from apps(CVS) as the cornerstone(CVS) didn't contain any files, just directories. Whenever I shutdown or restart the hsqldb block or Phoenix as a whole via JMX (mx4j) web interface, hsqldb doesn't get closed correctly but merely aborted. One can see this looking at the <dbschema-name>.properties-file, which is located in the directory from which hsqldb was started (for the current hsqldb-block this defaults to the <phoenix-home>/dist/bin-directory). The property "modified" has the value "yes", which indicates that hsqldb was suddenly aborted. (I copied some lines from the hsqldb user manual at the end of this posting as a reference.) Glancing over the sources of DefaultHypersonicSQL.java and HypersonicSQLHandler.java I can't see any start()- or stop()-method which might have contained the erroneous code or command upon shutdown, which left me with some confusion. I see, looking at some more descriptor and source files, that I don't understand enough about Phoenix Socket and Connection handling - furthermore I understand even less about mx4j and how stop and restart is invoked and what further processes happen. So, I currently feel not capable of providing a quick solution myself. Regards. Joerg p.s. copied from "hsqlRecovery.html": Database is aborted =================== This may happen by sudden power off, Ctrl+C in Windows, but may be simulated using the command SHUTDOWN IMMEDIATELY. * All files are closed; but the test.script file contains all information to re-do all changes. * The test.data file may be corrupt because the cache in memory was not written completely. * The test.properties still containes 'modified=yes' * All files are closed (maybe by the operating system) Database is closed correctly ============================ This may be done using the command SHUTDOWN, in the Standalone version using Connection.close() * The test.data file is written completely * The test.backup.new is created (containing the compressed test.data file) * The file test.script.new is created using the information in the database (and thus shrinks because no 'update' and 'delete' statements; only simple 'inserts'). * The entry 'modified' is set to 'yes-new-files' * The file test.script is deleted * The file test.script.new is renamed to test.script * The file test.backup is deleted * The file test.backup.new is renamed to test.backup * The entry 'modified' is set to 'no' -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
