From: Andrew May <amay@in...> - 2003-03-27 17:15:05
Hi, I've got an EAR with 16 deployment units and a large jar containing shared classes,
and when I redeploy the EAR JBoss keeps using more disk space.
When the server starts I see 16 copies of my shared lib under
tmp/deploy/server/ccsadm/deploy/my.ear/libs/shared.jar/, each numbered. When I redeploy
the EAR the old set of tmp files is deleted and a new set of 16 copies appears with higher
numbers. If I check the disk usage (du) for the tmp directories I see it drop whilst
redeploying then go back to the same value (i.e. it doesn't grow), but when I check for
free disk space (df) I see that I have about 60Mb less space after each redeployment. All
of this disk space is reclaimed after I stop the server.
Does this mean that something's holding onto a reference of the old jars when it
shouldn't? It's proving a real pain because we keep running out of disk space.
I'm running JBoss 3.2.0RC3 on Solaris with Sun's 1.4.1_01 JDK. I've noticed similar
problems with the 1.3.1 JDK and JBoss 3.0.6.
I've also got an Intel Linux box (Mandrake 9), and I tried to test if the same thing
happens. With JBoss 3.2.0RC3 and Sun's 1.4.1_01 JDK I only see 2 copies of my shared.jar
under the jboss tmp directory (2 of the deployment units are WARs). As far as I can tell
(it's less obvious because there's only 2 jars) it's also holding onto the disk space
after each redeployment.
Get latest updates about Open Source Projects, Conferences and News.