SAP Basis Tech Supports

Symptom
You want to use the Wily Introscope Agent on Linux x86_64 with IBM JDK 1.4.2 (as of SR10). You cannot start the J2EE Engine and it issues the following error message (std_server*.out):
Exception in thread “main” java/lang/NoSuchMethodError: java/lang/ClassLoader.isReflectCacheEnabled()Z
at java/lang/Class.lookupCachedMethod (Class.java:1659)
at java/lang/Class.getDeclaredMethod (Class.java:559)
at sun/misc/Signal.handle (Signal.java:199)
at java/lang/Terminator.setup (Terminator.java:69)
at java/lang/System.completeInitialization (System.java:67)
at java/lang/Thread.<init> (Thread.java:125)
JVMJ9VM015W Initialization error for library jclscar_23(14): JVMJ9VM009E J9VMDllMain failed
Other terms
Introscope, Wily, IBM, x86_64
Reason and Prerequisites
With SR10 of IBM JDK, a new Engine (2.3) was implemented and provided as a sidecar solution in the virtual machine (VM). In technical terms, two VMs are available as a result, whereby the user activates the new Engine with the option -Xjvm:j9vm23. Depending on the selected VM, the Introscope agent must now be configured with new parameters and integrated.
Solution

Updating an agent that was installed using SMD
If you installed the agent using SMD, it is sufficient to
execute the Introscope agent setup again for the system to be monitored. The setup then generates the AutoProbeConnector automatically.
For Solution Manager versions prior to Support Package 19, you must specifiy the path for the file classes.zip explicitly in the Setup UI (section AIX, also applicable to Linux). The path (for example, /opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip) depends on the SR of the JDK and can be found in the examples below.
As of Solution ManagerSupport Package 19, the parameter is adjusted automatically. The Introscope agent setup must be executed manually.
See also Note 797147.
Updating an agent that was installed without using SMD
To use this solution, you require at least the Introscope Agent in Version 7.2 (ISAGENT72*.SAR).
To correct the error, an additional parameter must be transferred both when the connectors are created and when the J2EE Server is started. Proceed as follows:
1. Unpack the Introscope Agent 7.2 (or higher) as described in Note 797147.2. If you want to operate the J2EE Server that is to be monitored with the new 2.3 Engine (as of SR10), add the following parameter (regardless of the IBM SR) when you create the connector.jar file:
SR10:
-Dcom.wily.autoprobe.prependToJVMRuntimePath=$JAVA_HOME/jre/bin/j9vm23/jclSC14/classes.zip
SR12:
-Dcom.wily.autoprobe.prependToJVMRuntimePath=$JAVA_HOME/jre/bin/j9vm/jclSC14/classes.zip
Note that you must set this parameter as the first parameter when you execute the “CreateAutoprobeConnector” step.
Note that the complete sequence -Dcom.wily. autoprobe.prependToJVMRuntimePath=<..> may not contain any blank characters.
Example (SR12):
java -Dcom.wily.autoprobe. prependToJVMRuntimePath=/opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip -jar Creat eAutoProbeConnector.jar -jvm /opt/IBMJava2-amd64-142 -output AutoProbeConnector.jar3. Use the configtool to add the same parameter to the other parameters of the VM that are to be monitored (ensure that you do not use any blank characters here either):
SR10:
-Dcom.wily.autoprobe. prependToJVMRuntimePath=/opt/IBMJava2-amd64-142/jre/bin/j9vm23/jclSC14/classes.zip
SR12 :
-Dcom.wily.autoprobe.prependToJVMRuntimePath=/opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip
Only use the option -Dcom.wily.autoprobe.prependToJVMRuntimePath for JDKs as of SR10 and in connection with the 2.3 Engine 2.3 (activated by parameter -Xjvm:j9vm23)
Note the following:
Depending on how the Introscope agent was installed initially, the path and the name of the generated connector archives may be different from the examples mentioned above. Check the FAQ (Note 797147) to determine the installation path of the Introscope agent. The name of the jar file (AutoProbeConnector.jar) generated with option -output must match the name of the jar file in the parameter -Xbootclasspath of the system to be monitored.