[ http://issues.apache.org/jira/browse/GERONIMO-1979?page=comments#action_12377698 ]
Prasad Kashyap commented on GERONIMO-1979: ------------------------------------------ Dain's comment in G-1925 (http://issues.apache.org/jira/browse/GERONIMO-1925#action_12377686 ) "I just committed a new class loader that should eliminate the file locks created by the class loader. To enable the new class loader, simply use -DXorg.apache.geronimo.NewClassLoader=true " I did a quick test with this new property. It solves the problem reported in G-1925. > Add custom class loader that does not leave open file locks > ----------------------------------------------------------- > > Key: GERONIMO-1979 > URL: http://issues.apache.org/jira/browse/GERONIMO-1979 > Project: Geronimo > Type: New Feature > Security: public(Regular issues) > Versions: 1.0 > Reporter: Dain Sundstrom > Assignee: Dain Sundstrom > Fix For: 1.1 > > We need a new class loader that does not leave open file locks when > destroyed. The URLClassLoader will only close the jar files and subsequently > release the file locks, when it is garbage collected. It is common for > programming mistake to leak references to classes (even the JVM has several > leaks), and these leaked classes have hard references to the class loader > which prevent the class loader from being garbage collected. On Windows the > jar files referred to by a URLClassLoader can not be modified or deleted > until the class loader is garbage collected which in too many cases means JVM > exits. This prevents redeployment from working since, the directory can not > be deleted. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
