Avoid using File.deleteOnExit in production code
------------------------------------------------
Key: GEOS-3752
URL: http://jira.codehaus.org/browse/GEOS-3752
Project: GeoServer
Issue Type: Bug
Components: WMS
Affects Versions: 2.0.0
Reporter: Andrea Aime
Assignee: Andrea Aime
Fix For: 2.0.2
Looking into a heap dump of a GeoServer that has been running for one month long under moderate load (20k requests a day) it's evident we're accumulating a high number of references to files that need to be deleted when the VM exists (90M of space used by them).
Looking into the GeoServer code this seems to be caused by WMS POST requests, in particular the GetMapXmlReader.
The file strategy can result in issues as well.
Look for calls to deleteOnExit and replace them with explicit deletes guarded by finally blocks or, at worst, finalizers instead.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira