ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Errors in Introscope doesn´t permit start the JVMs- Could not initialize class sun.security.util.SignatureFileVerifier

book

Article ID: 240384

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope) DX Application Performance Management CA Application Performance Management Agent (APM / Wily / Introscope)

Issue/Introduction

We are detecting an issue when we try to restart our JVM which contains an agent in its configuration (java arguments).

We have a WebSphere 8.5 JVM and we can see in the logs the following message:

4/26/22 05:28:48 PM IST [ERROR] [IntroscopeAgent.Agent] Unexpected error loading extension
java.lang.NoClassDefFoundError: Could not initialize class sun.security.util.SignatureFileVerifier

 

 

 

Cause

This error is reported a few times in teh log file 
/opt/WebSphere8.5/AppServer/java_1.7_32/jre/lib/rt.jar: error reading zip file
and first instance of the agent error is
/26/22 04:25:07 PM IST [ERROR] [IntroscopeAgent.Agent] Unexpected error loading extension 
ava.lang.NoClassDefFoundError: Could not initialize class sun.security.util.SignatureFileVerifier
 at java.util.jar.JarFile.initializeVerifier(JarFile.java:334)
The class (class sun.security.util.SignatureFileVerifier) should be in the rt.jar so looks like a corrupt java installation - or at least a corrupt rt.jar.

Environment

Release : 10.7.0

Component :

Resolution

Problem was due to corrupt Java installation - copying the Java install from a working server resolved the problem

Additional Information

33098954