i'm getting an error when i try to deploy my app as a jar:
Exception in thread "main" java.lang.SecurityException: invalid SHA1 signature file digest for com/microsoft/sqlserver/jdbc/SQLServerException.class
at sun.security.util.SignatureFileVerifier.verifySection(SignatureFileVerifier.java:438)
at sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:231)
at sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:176)
at java.util.jar.JarVerifier.processEntry(JarVerifier.java:234)
at java.util.jar.JarVerifier.update(JarVerifier.java:188)
at java.util.jar.JarFile.initializeVerifier(JarFile.java:321)
at java.util.jar.JarFile.getInputStream(JarFile.java:386)
at sun.misc.URLClassPath$JarLoader$2.getInputStream(URLClassPath.java:689)
at sun.misc.Resource.cachedInputStream(Resource.java:59)
at sun.misc.Resource.getByteBuffer(Resource.java:154)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:249)
at java.net.URLClassLoader.access$000(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
I've tried:
-merging the manifest files
-not adding a new manifest
-using multiple jars
-using a fat jar
-taking the manifest files out of /metadata and into the root of the jar
-all possible permutations of the above
i have to say, eclipse is excellent for coding, i could never code this fast in vim, but then again i've never had a problem in deployment writing code in vim either.
-Keon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
that is not an eclipse issue, but sounds like a mysql jdbc driver issue.
Could you try may get the latest release?
and possibly edit the sqlserver jar manifest to remove any signature related info?
I think also that if you "fatjar" the sqlserver jarwith your code, then that may lead to problems as the jar will contain partial signatures.
There are some post that may be of interest there btw: http://java-archive.org/showthread.php?p=405
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i'm getting an error when i try to deploy my app as a jar:
Exception in thread "main" java.lang.SecurityException: invalid SHA1 signature file digest for com/microsoft/sqlserver/jdbc/SQLServerException.class
at sun.security.util.SignatureFileVerifier.verifySection(SignatureFileVerifier.java:438)
at sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:231)
at sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:176)
at java.util.jar.JarVerifier.processEntry(JarVerifier.java:234)
at java.util.jar.JarVerifier.update(JarVerifier.java:188)
at java.util.jar.JarFile.initializeVerifier(JarFile.java:321)
at java.util.jar.JarFile.getInputStream(JarFile.java:386)
at sun.misc.URLClassPath$JarLoader$2.getInputStream(URLClassPath.java:689)
at sun.misc.Resource.cachedInputStream(Resource.java:59)
at sun.misc.Resource.getByteBuffer(Resource.java:154)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:249)
at java.net.URLClassLoader.access$000(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
I've tried:
-merging the manifest files
-not adding a new manifest
-using multiple jars
-using a fat jar
-taking the manifest files out of /metadata and into the root of the jar
-all possible permutations of the above
i have to say, eclipse is excellent for coding, i could never code this fast in vim, but then again i've never had a problem in deployment writing code in vim either.
-Keon
that is not an eclipse issue, but sounds like a mysql jdbc driver issue.
Could you try may get the latest release?
and possibly edit the sqlserver jar manifest to remove any signature related info?
I think also that if you "fatjar" the sqlserver jarwith your code, then that may lead to problems as the jar will contain partial signatures.
There are some post that may be of interest there btw: http://java-archive.org/showthread.php?p=405