I’m getting this Java error when launching the smart client after it downloads all the packages and immediately before the solution opening :
java.lang.NullPointerException
at java.util.jar.JarVerifier.mapSignersToCodeSource(Unknown Source)
at java.util.jar.JarVerifier.mapSignersToCodeSources(Unknown Source)
at java.util.jar.JarVerifier.getCodeSources(Unknown Source)
at java.util.jar.JarFile.getCodeSources(Unknown Source)
at java.util.jar.JavaUtilJarAccessImpl.getCodeSources(Unknown Source)
at com.sun.deploy.cache.DeployCacheJarAccessImpl.getCodeSources(Unknown Source)
at com.sun.javaws.security.SigningInfo.getCommonCodeSignersForJar(Unknown Source)
at com.sun.javaws.security.SigningInfo.check(Unknown Source)
at com.sun.javaws.LaunchDownload.checkSignedResourcesHelper(Unknown Source)
at com.sun.javaws.LaunchDownload.checkSignedResources(Unknown Source)
at com.sun.javaws.Launcher.prepareResources(Unknown Source)
at com.sun.javaws.Launcher.prepareAllResources(Unknown Source)
at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
at com.sun.javaws.Launcher.launch(Unknown Source)
at com.sun.javaws.Main.launchApp(Unknown Source)
at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
at com.sun.javaws.Main$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
I think it is a Java problem, it happened only after I updated to version 1.6.0_20. I set a previous installation (1.6.0_04) and the issue was no longer present.
What can be done since in most cases Java is updated automatically, breaking the application for our customers. Could it be a Servoy incompatibility problem? I’m using Servoy 4.1.5 - build 687.
You may find some pointers for resolving the issue you have reported in a topic on Java update 19: http://forum.servoy.com/viewtopic.php?f=6&t=13920&st=0&sk=t&sd=a&start=15.
I understand that Servoy engineers are working with Oracle/Sun to ensure that a future update will resolve current Java update issues. In the meantime, I have turned off auto-update for Java on all of the clients on my production system, and have reverted to the previous release of Java. This workaround is effective for us.
However, you may have detected something new with 20 which I have yet to see.
that exception most of the time means that within the same jnlp file there are different signers for the jars…
This can be resolved by using instead of inside the jnlp files
or remove signing of the jars in the plugin and sign them all with the same certificate.
I’ve tried all possible solutions documented in this forum. I’ve seen the other threads and I followed the instructions recently posted in the wiki page about Java Update 19.
I installed the new 4.1.6 version. I signed all my jars and I even removed all the plugins, beans, etc. from the application server. My Java cache is disabled, it’s downloading every time.
The very same error appears (the one I copied on the begging of the topic). I don’t know what to do next. I confirmed that downgrading the Java to version ‘_18’ we can get rid of the problem, but that’s not the solution we’re looking for all our customers.
As I said, I removed all the plugins and beans from the server and the problem still happened… The folders are empty. I don’t cache the Java, which means it downloads every single time.
i have no more idea’s
a default install of the latest servoy should just work out of the box with java 6u20 especially when you start with an empty cache.