[#GRAILS-2687] Verify that hsql database has shudown() called on it upon context destruction

Grails

Verify that hsql database has shudown() called on it upon context destruction

Created: 21/Mar/08 11:05 AM Updated: 30/May/08 05:33 AM

Component/s:

Persistence

Affects Version/s:

1.0.1

Fix Version/s:

1.0.3

Time Tracking:

Not Specified

Environment:

all

Issue Links:

Related

This issue is related to:

GRAILS-2544 Stopping Tomcat Context and doing undeploy does not completely shut down app, grails jars still locked

Description

« Hide

See hsql bug report at: http://sourceforge.net/tracker/index.php?func=detail&aid=1922315&group_id=23316&atid=378131

Just need to make sure that grails calls shutdown() on the hsql database during context destruction? If this issue is addressed, this will ensure that this Thread is cleaned up properly and a potential leak is avoided in a hot-deploy environment.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Graeme Rocher added a comment - 30/May/08 05:33 AM

As per HSQLDB docs we now call this code on context shutdown:

if(dbName == 'HSQL Database Engine') {
                    connection.createStatement().executeUpdate('SHUTDOWN')
                }