xplanner

Support for HSQDB (migration, startup/shutdown)

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 0.7
  • Fix Version/s: 0.7
  • Component/s: Database
  • Labels:
    None
  • JDK version and platform:
    Sun JDK 1.4.2_06 for linux
  • Database:
    hsqldb
  • Application server:
    xplanner 0.7b1 standalone

Description

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.
  1. File
    catalina.out
    01/Mar/06 8:32 AM
    1.64 MB
    Edward Shryane

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Edward Shryane added a comment -
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

Show
Edward Shryane added a comment - 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
Hide
Permalink
Edward Shryane added a comment -
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?
Show
Edward Shryane added a comment - 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?
Hide
Permalink
Jacques Morel added a comment -
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.
Show
Jacques Morel added a comment - 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.
Hide
Permalink
Jacques Morel added a comment -
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.
Show
Jacques Morel added a comment - 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.
Hide
Permalink
Edward Shryane added a comment -
Thanks for fixing this.
Show
Edward Shryane added a comment - Thanks for fixing this.

People

  • Assignee:
    Jacques Morel
    Reporter:
    Edward Shryane
Vote (2)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: