Details
-
Type:
Task
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0.1
-
Fix Version/s: 1.0.3
-
Component/s: Persistence
-
Labels:None
-
Environment:all
Description
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.
Issue Links
| This issue is related to: | ||||
| GRAILS-2544 | Stopping Tomcat Context and doing undeploy does not completely shut down app, grails jars still locked |
|
|
|
As per HSQLDB docs we now call this code on context shutdown:
if(dbName == 'HSQL Database Engine') { connection.createStatement().executeUpdate('SHUTDOWN') }if(dbName == 'HSQL Database Engine') { connection.createStatement().executeUpdate('SHUTDOWN') }