Hi,

I was using my own PersistenceManager singleton which wrapped a Hibernate SessionFactory and did a session.open and session.close for all db operations and then switched all my DAOs to extend from Spring's HibernateDaoSupport (Hibernate 3). I had also been using in-memory HSQLDB with Tomcat in a web application. What I noticed is that before the migration the data would actually persist between successive Tomcat restarts, but now it seems it doesn't. It seems I now have to run HSQLDB in stand-alone server mode... is this normal?

Thanks, Jason

I should mention that the only difference is before I was using

hibernate.connection.url=jdbc:hsqldb:/database/gridsphere

to point to the flat file DB and now I've been forced to use

hibernate.connection.url=jdbc:hsqldb:hsql://localhost

in order for the data to be persisted between server restarts

Read the HSQL documentation and note the difference between CREATE TABLE and CREATE CACHED TABLE. Also you should be running it in stand alone server mode, the documentation clearly states that in memory mode is best for small apps not for production use in multiuser environments.