Can't find what you need?


• Ask the Community
• Create a Case
Reset Search
 

 

Article

Updated to Java 8 1.41 and unable to launch NetSight Java applications

« Go Back

Information

 
TitleUpdated to Java 8 1.41 and unable to launch NetSight Java applications
Symptoms
  • "Unable to launch application" message after updating Java
  • com.sun.deploy.net.JARSigningException: Could not verify signing in resource:<Resource varies>
  • #### Could not verify signing in resource: <Resource Varies>
Environment
  • NetSight
  • Extreme Management Center
  • Java application
Cause
Java 8 update 141 disabled sha1 TLS certificates, some jar files are signed with sha1 certificates
Resolution
Upgrade to Java update 144. Java update 141 included a bug fix that caused issues with opening JAR files. 

Per Java Release notes: 

"Bug Fixes

security-libs/javax.net.ssl
java.util.zip.ZipFile.getEntry() now always returns the ZipEntry instance with a / ended entry name for directory entry

The java.util.zip.ZipEntry API doc specifies "A directory entry is defined to be one whose name ends with a /". However, in previous JDK releases, java.util.zip.ZipFile.getEntry(String entryName) may return a ZipEntry instance with an entry name that does not end with / for an existing zip directory entry when the passed in argument entryName does not end with a /, and there is a matching zip directory entry with name entryName + / in the zip file.
With this release, the name of the ZipEntry instance returned from java.util.zip.ZipFile.getEntry() always ends with / for any zip directory entry.

To revert to the previous behavior, set the system property jdk.util.zip.ensureTrailingSlash to "false".

This change was made in order to fix a regression introduced in JDK 8u141 when verifying signed JARs that has caused some WebStart applications to fail to load."
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255