Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 3004, 1 year ago
via Oracle Community by 259686, 1 year ago
via Google Groups by Paul Schwann, 1 month ago
jzentry == 0
via nabble.com by Unknown author, 1 year ago
jzentry == 0, > > jzfile = 118335776, > > total = 2482, > > name = tools\tomcat\4.1.31\temp\jar_cache53708.tmp, > > i = 34, > > message = invalid LOC header (bad signature)
via Netbeans Bugzilla by heidiamiri, 7 months ago
via Netbeans Bugzilla by jbaker, 7 months ago
java.lang.InternalError: jzentry == 0	at java.util.zip.ZipFile$2.nextElement(ZipFile.java:292)	at java.util.jar.JarFile$1.nextElement(JarFile.java:193)	at weblogic.utils.jars.VirtualJarFile$1.next(VirtualJarFile.java:91)	at weblogic.connector.descriptor.JarFilesMBeanImpl.(JarFilesMBeanImpl.java:32)	at weblogic.connector.descriptor.ConnectorDescriptorMBeanImpl.getConnectorDescriptorMBean(ConnectorDescriptorMBeanImpl.java:183)	at weblogic.connector.descriptor.ConnectorDescriptorMBeanImpl.getConnectorDescriptorMBean(ConnectorDescriptorMBeanImpl.java:59)	at weblogic.connector.deploy.ConnectorModule.loadDescriptor(ConnectorModule.java:136)	at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:714)	at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)	at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1062)	at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:730)	at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)	at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)	at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)