On 07/12/2012 09:37 AM, accordeuro wrote:
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) j java.util.zip.ZipFile.getEntry(JLjava/lang/String;Z)J+0 j java.util.zip.ZipFile.getEntry(Ljava/lang/String;)Ljava/util/zip/ZipEntry;+31 j java.util.jar.JarFile.getEntry(Ljava/lang/String;)Ljava/util/zip/ZipEntry;+2 j java.util.jar.JarFile.getJarEntry(Ljava/lang/String;)Ljava/util/jar/JarEntry;+2 j sun.misc.URLClassPath$JarLoader.getResource(Ljava/lang/String;Z)Lsun/misc/Resource;+48 ...j org.apache.tools.ant.util.CollectionUtils$CompoundEnumeration.hasMoreElements()Z+4 ...j java.lang.reflect.Method.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+161 j org.apache.tools.ant.dispatch.DispatchUtils.execute(Ljava/lang/Object;)V+518 j org.apache.tools.ant.Task.perform()V+22
The Oracle JRE's implementation of ZipFile is designed to assume that a ZIP is never modified or deleted while open. This is a safe assumption for static program JARs, but if you have a process which first _builds_ a JAR and then _runs_ something out of it, you have a potential problem: if the JAR is deleted or rebuilt while the first run task is still in progress, the JVM can crash with this error. Here it looks like you have a job which builds some JAR with an Ant task and then runs the task; if you try to run this twice _in the same workspace_ (are you?) then a crash is to be expected.
