You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Kevan Miller (JIRA)" <de...@geronimo.apache.org> on 2005/11/21 17:16:41 UTC

[jira] Commented: (GERONIMO-777) Deployment files not removed on Windows

    [ http://issues.apache.org/jira/browse/GERONIMO-777?page=comments#action_12358158 ] 

Kevan Miller commented on GERONIMO-777:
---------------------------------------

I'm running on Win XP. Deploy/undeploy of some simple jsp's and servlets is properly cleaning up the config-store directories. It's possible that the recent URLJarFile cleanup (http://issues.apache.org/jira/browse/GERONIMO-1177) may be helping. But I haven't done a post-analysis

I do, however, see directories (i.e. 3) remaining after each deploy/undeploy of DayTrader. A while back testing deploy/undeploy memory leaks, I saw DayTrader deploy config-store directories were taking up 9 gigs worth of my hard-drive 8-{

I'd heard some claims that this problem had been fixed, but it seems not...

I can delete the directories by hand after deploy/undeploy while Geronimo is running. So, any file locks (if that's the problem) seem to be transient.

It would be useful to confirm that this is a Windows-only phenomenon...

I'm currently looking into some DayTrader runtime issues, but will include this in my investigations.

> Deployment files not removed on Windows
> ---------------------------------------
>
>          Key: GERONIMO-777
>          URL: http://issues.apache.org/jira/browse/GERONIMO-777
>      Project: Geronimo
>         Type: Bug
>     Versions: 1.0-M3, 1.0-M4, 1.0-M5
>  Environment: Windows
>     Reporter: Jeremy Boynes
>     Assignee: John Sisson
>      Fix For: 1.0

>
> When running on Windows, deployment leaves behind files and directories in the user's temp directory. Due to the way temp file names are allocated, this can result in deployment failures with an unintuitive AccessDenied IOException. These files cannot be removed without shutting down the server.

-- 
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