Unable to start WebSphere instance even when is not instrumented by the Java Agent
search cancel

Unable to start WebSphere instance even when is not instrumented by the Java Agent

book

Article ID: 17906

calendar_today

Updated On:

Products

DX Operational Observability DX Application Performance Management DX SaaS

Issue/Introduction

On one instrumented WebSphere instances does not start, even after uninstalling the Introscope Agent. Additionally, a different node in the cluster on the same machine does not start, and it is not instrumented.

When the first server is started and then trying to start the second server, the following error message appears, even though it is not configured for Introscope and it throws a "class not found" error in the logs:

SRVE0232E: Internal Server Error.
Exception Message: [com.wily.introscope.agent.trace.IMethodTracer]
or
java.lang.NoClassDefFoundError: com.wily.introscope.agent.AgentShim
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:74)

Environment

DX O2 Java Agent

Cause

This issue is the result of the IBM Class Sharing feature implemented in the IBM 1.5 JVM or higher JRE's. (Even in 1.4.2 if J9 VM.)

The issue manifests itself in the following ways:

  • ClassNotFound exceptions or nodes not able to start up after removing Introscope.

  • Two nodes (only one Wily enabled) running on the same machine (managed through a node agent) with the no instrumented one failing to startup complaining about Wily classes.

Resolution

Use the -Xshareclasses option:

  • Add -Xshareclasses:none to all servers using Wily software so that classes modified by Wily are not stored in the shared class cache.

  • Add -Xshareclasses:name=wily to all servers using Wily software so that classes modified by Wily are stored in their own shared class cache.