Hi,

It is not clear how related this is to jetty.

I have noticed that jetty seems to unpack a war into a folder and then some
class loader looks to read those jar files (this is all fine). What I have
noticed though is for each jar file a bit of heap memory is used.

It looks like a ZipFile$Source is held open and it hangs on to memory for
every jar file that is in the war file. The amount consumed seems to be
proportional to the size of the jar.

Have you noticed this or ever looked into this? Is it possible to prevent
the JVM from doing this?

Many thanks

-Luke
_______________________________________________
jetty-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/jetty-users

Reply via email to