Smarts NCM: NCM Client doesn't launch and errors out with "could not verify signing in resource: https://app_server_address:8880/voyence/lib/xalan-2.6.0.jar"
book
Article ID: 331223
calendar_today
Updated On:
Products
VMware Smart Assurance
Issue/Introduction
Symptoms:
Users will notice that Network Configuration Manager doesn't launch with Java 1.8.0_141 and then will error out with the following error below:
com.sun.deploy.net.JARSigningException: Could not verify signing in resource: https://app_server_address:8880/voyence/lib/xalan-2.6.0.jar at com.sun.deploy.security.JarVerifier.authenticateJarEntry(Unknown Source) at com.sun.deploy.security.EnhancedJarVerifier.validate(Unknown Source) at com.sun.deploy.cache.CacheEntry.processJar(Unknown Source) at com.sun.deploy.cache.CacheEntry.access$2700(Unknown Source) at com.sun.deploy.cache.CacheEntry$7.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at com.sun.deploy.cache.CacheEntry.writeFileToDisk(Unknown Source) 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.downloadResource(Unknown Source) at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source) at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source) at com.sun.javaws.LaunchDownload$DownloadTask.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
Environment
VMware Smart Assurance - NCM
Cause
NCM UI doesn't launch with Java 1.8.0_141 due to a regression introduced in JDK 1.8.0_141 when verifying signed JARs that has caused some WebStart applications to fail to load.
Resolution
To resolve the issue please upgrade to Java 1.8.0_144.
For more details please check "Bug Fixes" section from link: http://www.oracle.com/technetwork/java/javase/8u144-relnotes-3838694.html