AS 6 CR1 temp files

[nickarls]

Are the temporary deploy files cleaned out at all? Is there a way of limiting them? I tried nuking the tmp/data/work directories and my "recycling" box now says 223789 items (still not done). It might always have been like this but since the last major version of vfs(?) the number of temp files appears to have exploded.

[jaikiran]

The "data" and "work" directories are used for different purposes and won't be cleaned by default (there are reasons for that). However, the "tmp" folder should ideally get cleaned on each server restart. Do you have an example of what's left behind in the tmp folders? Which operating system are you on and which Java version and vendor?

[nickarls]

The delete was almost done now but I saw a vfs directory with lots of vfsinmemory, shrinkwrap and automount directories. It's a dev AS so there are lots of hot-deployments (including JRebel usage). It's a Sun HotSpot 64b 1.6.0_20

[mreasy]

Can also confirm, that the jboss.server.temp.dir is not cleaned or overwritten - neither on a clean shutdown, nor on restart, so over time it grows and grows...

Seen on Windows (7) and  Linux (RHEL 5).

[jaikiran]

I just did a quick check with 6.0 CR1 and latest AS trunk. Although there are sub folders which are left behind in the "tmp" folder, all those sub folders are empty when the server gets shutdown. The files within those subfolders are (as expected) cleared on my system during the shutdown.

Are you guys seeing files being left behind in those folders?

[nickarls]

Started CR1 with a deployment, stopped it, got around 80Mb of stuff in vfs/automount/ jar files. Many empy dirs, too.

[gbo3006]

Also suffering from this issue. Is there an open jira, or should I open one?

[jaikiran]

Please create one

[gbo3006]

https://jira.jboss.org/browse/JBAS-8718