application failed to start : Error in dependencyCheck java.util.zip.ZipException: invalid entry CRC

2008-08-08 Thread [EMAIL PROTECTED]
attempting to run application on Tomcat 5.5 server (Fails to load at context path) I see this in the catalina.log Google search suggests a zip file error with the .war - but I have only used an exploded tree and removed previous .war file. Any suggestions? -- James Stanbridge Kellstan IM:

Re: application failed to start : Error in dependencyCheck java.util.zip.ZipException: invalid entry CRC

2008-08-08 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 James, [EMAIL PROTECTED] wrote: | attempting to run application on Tomcat 5.5 server (Fails to load at | context path) I see this in the catalina.log | | Google search suggests a zip file error with the .war - but I have | only used an exploded tree

Error in dependencyCheck

2006-12-19 Thread Assaf Flatto
- Starting Servlet Engine: Apache Tomcat/5.5.17 2006-12-19 18:26:14,258 [main] INFO org.apache.catalina.core.StandardHost - XML validation disabled 2006-12-19 18:26:14,475 [main] ERROR org.apache.catalina.core.StandardContext - Error in dependencyCheck java.util.zip.ZipException: missing

[SPAM ?]Re: [SPAM ?][SPAM ?]Re: [SPAM ?]Error in dependencyCheck when using Connection pooling

2006-08-15 Thread Tom Bednarz
. Tom Mark Eggers wrote: From looking for this error message with Google, it appears that there is a problem with the manifest information in your jar file. Use the following two search items in Google: java.io.IOException invalid header field error in dependencycheck What JDBC driver (DB

[SPAM ?]Error in dependencyCheck when using Connection pooling

2006-08-14 Thread Tom Bednarz
I get a very strange error when starting my web-app: --- 14.08.2006 18:38:25 org.apache.catalina.core.StandardContext start SCHWERWIEGEND: Error in dependencyCheck java.io.IOException: invalid header field at java.util.jar.Attributes.read(Attributes.java:393

Re: [SPAM ?]Error in dependencyCheck when using Connection pooling

2006-08-14 Thread Mark Eggers
From looking for this error message with Google, it appears that there is a problem with the manifest information in your jar file. Use the following two search items in Google: java.io.IOException invalid header field error in dependencycheck What JDBC driver (DB and version), Tomcat version