jetty and 'hot-deploy', not freeing diskspace?

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

jetty and 'hot-deploy', not freeing diskspace?

Brian Reichert
We're employing the 'hot deploy' feature in jetty to redeploy an
updated webapp.

What we're observing is that the redeployment doesn't discard the
disk resources of the prior deployment.

Using 'lsof' as such:

  lsof -nP +L1 /var | grep /var | grep '(deleted)' | less

We can see dozens of old deployments (old extracted war files?), like this:

  java      26734        root   82r   REG    8,6   575389     0  32470
  java      26734        root  110r   REG    8,6   575389     0  32561
  java      26734        root  318r   REG    8,6   575389     0  40227

As the JVM is still holding a reference, the disk space never frees, and our
/var/ partition eventually fills. :/

Do other people see this?

Are we doing this wrong?  All we did was modify the scanInterval setting to
a nonzero value.

Is there some configuration switch we can throw to coerce the JVM
to really release these resources, or are we stuck waiting for the
GC to eventually cleanup?

Details of our environment:


  OpenJDK Runtime Environment (build 1.8.0_71-b15)

  CentOS release 6.7 (Final)

  # uname -r

Brian Reichert <[hidden email]>
BSD admin/developer at large
jetty-users mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit