[kepler-dev] [Bug 5437] New: provenance hsqldb database doesn't behave as though it's properly shutdown when in server mode

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5437

           Summary: provenance hsqldb database doesn't behave as though
                    it's properly shutdown when in server mode
           Product: Kepler
           Version: 2.1.0
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: provenance
        AssignedTo: crawl at sdsc.edu
        ReportedBy: barseghian at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org
   Estimated Hours: 0.0


When using server-mode hsqldb provenance, kepler shutdown goes very fast, the
.log file remains, and subsequent kepler startup takes a long time as the log
file is processed. This is the opposite of the desired/expected behavior and
how file-mode hsqldb works.
It seems like we're doing the right things for a proper shutdown to occur, and
checking server.getState() in HSQL.shutdownServers() returns that all databases
have been shutdown, yet the log file is supposed to be processed and removed if
a proper SHUTDOWN occurs according to the 1.8 docs, and this is not happening.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.