Sudden issue with tools plugin stopping smart client

Classic Servoy
21

Harjo,

could this be the case for the client you talk about?

IT2Be:
Today I learned it can have to do with early versions of Windows 7 and Vista that don’t have a ‘current’ crypto32.dll with these root certificates.

22

No, at that company, they have Windows XP only.

When we gave the machines, real internet, everything was fine, but as soon as we did’nt the client refused to start.

23

I am gettings this issue now, after I upgraded to the latest calendar plugin (It2Be) and to Servoy 5.1.4

com.sun.deploy.net.JARSigningException: Could not verify signing in resource: (http://ibisappprod:8080/plugins/it2be-calendar/migcalendar.jar, 1278439245489)
    at com.sun.deploy.cache.CacheEntry$9.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sun.deploy.cache.CacheEntry.writeFileToDisk(Unknown Source)
    at com.sun.deploy.cache.Cache.downloadResourceToTempFile(Unknown Source)
    at com.sun.deploy.cache.Cache.downloadResourceToCache(Unknown Source)
    at com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source)
    at com.sun.deploy.net.DownloadEngine.getCacheEntry(Unknown Source)
    at com.sun.deploy.net.DownloadEngine.getCacheEntry(Unknown Source)
    at com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(Unknown Source)
    at com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(Unknown Source)
    at com.sun.deploy.net.DownloadEngine.getResource(Unknown Source)
    at com.sun.javaws.LaunchDownload$DownloadTask.call(Unknown Source)
    at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
    at java.util.concurrent.FutureTask.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

To keep working I replaced the migcalendar.jar with an older version.

Regards,

24

Your issue has nothing to do with the original issue Hans. You can see what it is about by searching for the error ‘JARSigningException: Could not verify signing in resource’.

Possible reasons and solutions for the issue might be:

  1. A client reported an issue due to (old because it is not used anymore) it2be jars and folders in developer/features and developer/plugins. Although highly unlikely it does not hurt to remove it.
  2. I know developers tend to archive older versions of (our) components somewhere else under the Servoy root folder.
    Unless stored in an archive file like done by our Component Manager when you update you should never do this.
    It depends on where you store those files but when Servoy Server ‘sees’ them and the signature is old or missing you could see what you see.
  3. You use another version of the migcalendar.jar than the (last) one distributed by us.
  4. Maybe the jar file is not overwritten due to user rights.

Hope this helps