History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: XPR-233
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Critical Critical
Assignee: Jacques Morel
Reporter: Edward Shryane
Votes: 2
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
xplanner

Support for HSQDB (migration, startup/shutdown)

Created: 01/Mar/06 08:14 AM   Updated: 23/May/06 05:23 AM
Component/s: Database
Affects Version/s: 0.7
Fix Version/s: 0.7

Time Tracking:
Not Specified

File Attachments: 1. File catalina.out (1.64 Mb)


JDK version and platform: Sun JDK 1.4.2_06 for linux
Database: hsqldb
Application server: xplanner 0.7b1 standalone


 Description  « Hide
Running xplanner 0.7b1 standalone server, hsqldb stopped writing data to hsqldb.script file after a few days (also no .backup or .data file to restore from). When the server was stopped, hsqldb didn't write the current database in memory to disk, and data was lost.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Edward Shryane - 01/Mar/06 08:32 AM
added catalina.out.
sequence of events as follows:

(1) Jan 20, 2006 12:48:00 PM: server started

(2) last database update in xplanner.script on Jan 31st, 12:12

(3) Feb 27, 2006 10:39:30 PM: server stopped

(4) missing row errors in database on Feb 28


Edward Shryane - 01/Mar/06 10:03 AM
I've been reading the hsqldb documentation on when data is written to disk, WRITE_DELAY was set to 20 seconds, but this failed somehow. Also, data was not written on the server shutdown. Is the SQL command SHUTDOWN explicitly issued to hsqldb before the tomcat shutdown?

A new connection property shutdown was introduced to hsqldb 1.8.0 RC12, which, if true, will cause the engine to perform a SHUTDOWN on the database when the last connection is closed. Would this be an appropriate fix?

Jacques Morel - 18/Mar/06 02:40 AM
Upgraded to 1.8.0.2
Created context listener that starts a threaded server and closes it when context shuts down. This allows external client to access the database which is not the case for the pure embedded mode.

Jacques Morel - 18/Mar/06 02:57 AM
Edward, I don't think you will mind that I hijacked your issue into a bigger one: the full support of HSQLDB.
Since a lot of people used HSQLDB in production and since I always had in mind to support it, I want to do it right.

Edward Shryane - 23/May/06 05:23 AM
Thanks for fixing this.