If you are currently using version 5.x.x, we advise you to upgrade to the latest version before the EOL date. You can find the latest documentation here.
Troubleshoot the Java configuration
Overview
Interactions between different platforms, plug-ins, and Java implementations may often cause small errors when you configure the Java environment. This topic covers the most common errors and walks you through how to resolve them.
JVMManager errors
Failed to load JVMManager because of a component version mismatch
<Sun Jul 7 22:00:53> ERROR: JVMManager Unable to open [geneos-plugins.jar] because [No such file or directory] <Sun Jul 7 22:00:53> ERROR: JVMManager Failed to retrieve file version information from [geneos-plugins.jar] <Sun Jul 7 22:00:53> ERROR: JVMManager Version mismatch: netprobe[GA4.10.2-190314] - liblaunchpad.so[GA4.10.2-190314] - geneos-plugins.jar[##-000000] <Sun Jul 7 22:00:53> ERROR: SamplerManager::_addSamplers Failed to load JVMManager because of a component version mismatch
The component version mismatch can occur in the following scenarios:
- Library versions incompatible with the Netprobe
- Netprobe cannot locate the required libraries to run the JVM
Library versions incompatible with the Netprobe
A version mismatch can happen when only certain library files are updated in the Netprobe package. Libraries can differ from version to version. The best practice is to update the entire Netprobe.
Netprobe cannot locate the required libraries to run the JVM
The Netprobe can fail to locate the required libraries when you execute it from outside its installation directory.
If you need to execute the Netprobe from a different directory, then use the GENEOS_JARS and GENEOS_LIBS environment variables to point to the required libraries.
The environment variables must contain the absolute path to the required libraries, and must be exported to the Netprobe start script.
For guidance, see the following sections:
- Configure the Java environment in Configure the Java environment to set
GENEOS_JARS. - Configure the Java environment in Configure the Java environment to set
GENEOS_LIBS.
Failed to create LaunchPad class
<Fri Oct 11 16:53:20> ERROR: JVMManager Failed to create LaunchPad class
The LaunchPad class error can occur in the following scenarios:
Netprobe cannot locate geneos-plugins.jar
If you are executing the Netprobe in its installation directory, check that the geneos-plugins.jar file exists. If it does not, then reinstall the Netprobe package.
If you need to execute the Netprobe from a different directory, then use the GENEOS_JARS and GENEOS_LIBS environment variables to point to the required libraries.
The environment variables must contain the absolute path to the required libraries, and must be exported to the Netprobe start script.
For guidance, see the following sections:
- Configure the Java environment in Configure the Java environment to set
GENEOS_JARS. - Configure the Java environment in Configure the Java environment to set
GENEOS_LIBS.
Incompatible Java version
Check that you are using a supported version of Java for the component and platform you are using. For guidance, see the Java support in Geneos Compatibility Matrix.
UnsatisfiedLinkError exceptions
If you get java.lang.UnsatisfiedLinkError exceptions when using the Java interface with the IBM Java VM (J9VM) on AIX, then you need to set the LIBPATH to the location of the native shared libraries. For more information, see Set the environment variables in Configure the Java environment.
JVMDataFormatter error
<Mon Nov 25 14:53:27> ERROR: JVMDataFormatter Could not find class Could not initialize class com.itrsgroup.jmx.formatter.JVMDataFormatter
The JVMDataFormatter error can occur when the value of the JAVA_HOME environment variable is incorrect. The value must contain the absolute path of the Java binary's jre folder.
Example of an incorrect path:
export JAVA_HOME=/opt/lib/java/oracle/current
Example of a correct path:
export JAVA_HOME=/opt/lib/java/oracle/current/jre
For guidance in setting up the JAVA_HOME environment variable, see Configure the Java environment in Configure the Java environment.
Note: As a best practice, check that you are using a supported version of Java for the component and platform you are using. For guidance, see the Java support in Geneos Compatibility Matrix.