Have developed solution on laptop & now deployed onto Server PC so that client can access from own office for testing. But cannot log into solution from laptop due to following error
An error occurred while launching/running the application.
JNLPException[category: Download Error : Exception: java.lang.SecurityException: SHA1 digest error for com/servoy/j2db/persistence/Relation.class : LaunchDesc: null ]
at com.sun.javaws.security.SigningInfo.checkSigning(Unknown Source)
at com.sun.javaws.cache.DownloadProtocol$RetrieveAction.actionDownload(Unknown Source)
at com.sun.javaws.cache.DownloadProtocol.doDownload(Unknown Source)
at com.sun.javaws.cache.DownloadProtocol.getResource(Unknown Source)
at com.sun.javaws.LaunchDownload.downloadJarFiles(Unknown Source)
at com.sun.javaws.LaunchDownload.downloadEagerorAll(Unknown Source)
at com.sun.javaws.Launcher.downloadResources(Unknown Source)
at com.sun.javaws.Launcher.handleApplicationDesc(Unknown Source)
at com.sun.javaws.Launcher.handleLaunchFile(Unknown Source)
at com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Had problems with initial Server PC installation and eventually uninstalled Servoy and just copied across complete directory. Could it be that this is causing the problem ?
Another laptop loads solution from Server without a problem. Credits to the Dev Team - using this 3yr old Sony laptop with 256mb Ram the speed is stunning - text searches on 39,000 documents (@ 60mb) taking just 5-6 secs & client blown away!!! Great work.
Regards
Graham Greensall
Worxinfo Ltd
Laptop & Server PC both on:
Servoy Developer
Version R2 2.2rc3-build 321
Java version 1.5.0_02-b09 (Windows XP)
Sorry - wrong info in previous post regarding Server Java version - brain getting fried and its only 2am
After reading other posts I removed Java 1.5 so that Server PC now running 1.4.2_06-b03(Windows XP) - the laptop that does connect also on same Java version.
I could rollback Java on this laptop - but do not know what version is on clients machines so would appreciate any ideas.
I can remember we did a use a new certificate with more known trusted root. (back in 2005)
“trusted root” means default known by all Java Suppliers like Apple/Sun.
As far as I know this is not a problem for other Mac users, did you not replace Root certificates on your system? (which might be used from Java)
I think this is a known problem since 3.5. On the server you will have to either downgrade Java to maybe 1.5.0_07 or upgrade to Java 6. In our case, upgrading to Java 6 healed the issue.