I am a bit confused about JVM behavior when loading a jar from a remote disk drive:
Is it true that (on Sun JVM) when a class is loaded, it is stored into a local cache (file?) where it remains even AFTER the appliaction halts?
When using remote jar files (on a different PC in a very slow local network) first execution of my code takes several seconds to execute (profiling shows it's downloading the classes from jar), while any subsequent execution is much faster (and no network data flow is detected) - it obviously loads classes from the local computer.
It makes me think all the classes get stored in the java cache, but the effect takes only some 20 seconds after which the class has to be loaded from the remote classpath again (with the lag). Any ideas?