Hi Phillip,
from http://hsqldb.sourceforge.net/doc/guide/ch01.html#N10190
" All databases running in different modes can be closed with the
SHUTDOWN command, issued as an SQL query. In 1.7.2, in-process databases
are no longer closed when the last connection to the database is
explicitly closed via JDBC, a SHUTDOWN is required. When SHUTDOWN is
issued, all active transactions are rolled back. A special form of
closing the database is via the SHUTDOWN COMPACT command. This command
rewrites the .data file that contains the information stored in CACHED
tables and compacts it to size. This command should be issued
periodically, especially when lots of inserts, updates or deletes are
performed on the cached tables. Changes to the structure of the
database, such as dropping or modifying tables or indexes also create
large amounts of unused space that can be reclaimed using this command."
Having said that I'm not the HSQLDB expert - invoking stop() might solve
the problem but I prefer the SHUTDOWN since it compacts the database on
the fly.
Cheers,
Siegfried Goeschl
phillip rhodes wrote:
I am not aware of the ability to issue a sql shutdown
to an in-process HSQL instance.
In your case, it would appear to me that you will have
to stop the server.
HTH
--- Siegfried Goeschl <[EMAIL PROTECTED]>
wrote:
Hi Sebastien,
I think you need to issue a SQL shutdown command for
HSQLDB which also
compacts the database
Cheers,
Siegfried Goeschl
Sebastien Arbogast wrote:
Hi,
I'm using Codeczar tomcat plugin to manipulate my
tomcat server for my
web application.
So when I have to recompile some Java class while
my Tomcat server is
running I want to execute the following procedure :
maven tomcat:stop
maven war:webapp
maven tomcat:start
But then when I try to access my database (HSQLDB
in file protocol,
In-process mode) through my application, I get the
following error
message :
The database is already in use by another process:
[EMAIL PROTECTED]
=C:\dev\pfe\schaman\target\webapp\WEB-INF\db\schamandb.lck,
exists=true, locked=false, valid=false, fl =null]:
The problem seems to be that when the application
is stopped, the lock
on schamandb.lck is not released. Does anyone know
how to solve this
situation or do I have to stop the server everytime
I have something
to recompile ?
My configuration is the following :
- HSQLDB 1.7.3.3
- Maven 1.0.2
- maven-tomcat-plugin version 1.1
Thx in advance.
---------------------------------------------------------------------
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]