IBM Support

Error: Not able to find or start JVM (Java Virtual Machine), library jvm or javai, from unix agent

Troubleshooting


Problem

This technote explains how to resolve an error: Not able to find or start JVM (Java Virtual Machine), library jvm or javai, from a UNIX agent when using IBM Rational TestManager (TM).

Symptom

When executing a Java script on an UNIX agent, following error is encountered:


    TSEE #001: fatal user initialization error:
    [22.3.6.224]: SessionOpen() failed for Test Script Execution Adaptor: rttseajava: [22.3.9.259]: Java SessionOpen() failed
    Not able to find or start JVM (Java Virtual Machine), library jvm or javai

Cause

The library environment path LD_LIBRARY_PATH is not correctly set.

Diagnosing The Problem

When TestManager plays back a Java test script, it must be able to load a Java virtual machine (jvm.dll or jvm.so). On Microsoft Windows systems, the location of the JVM can be specified on the system path. If no JVM is found using the system path, TestManager will attempt to locate one relative to the location of java.exe. On UNIX systems, the location of the JVM must be specified using the library environment variable appropriate for your system. For example, on Solaris, you must indicate the location of the JVM using the environment variable LD_LIBRARY_PATH.

Windows Example
d:\jdk1.x\jre\bin\classic

Solaris Example
/usr/jdk1.x/jre/lib/sparc/classic:/usr/jdk1.2.2/jre/lib/sparc/native_threads

If you fail to specify the location of the jvm, and we are unable to locate it relative to the installation of the JDK, you will receive the following error message at playback:

[1.1.5.172] Execution Adaptor rttseajava: couldn't retrieve test script info for SabreClient (datapath = c:\testscripts): [1.3.9.259]: Java() failed

Not able to find or start JVM (Java Virtual Machine), library jvm or javai

[1.1.4.52] RTmaster run not executed due to fatal workload description errors.

*** RTmaster Exiting (1 error, 0 warnings)

Resolving The Problem

To resolve this issue:

  1. Set the path reference on the UNIX machine.
  2. Set the path reference in the Suite's sys environment setting (Test Manager -> Suite -> Edit Settings -> Sys Environment Variables.)

[{"Product":{"code":"SSSHVH","label":"Rational TestManager"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Test Agent","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF016","label":"Linux"}],"Version":"2003.06.00;2003.06.10;2003.06.12;2003.06.13;2003.06.14;2003.06.15;2003.06.16;7.0;7.0.0.1;7.0.0.2;7.0.0.3;7.0.0.4;7.0.1;7.0.1.1;7.0.1.2;7.0.1.3;7.0.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Historical Number

24396

Document Information

More support for:
Rational TestManager

Software version:
2003.06.00, 2003.06.10, 2003.06.12, 2003.06.13, 2003.06.14, 2003.06.15, 2003.06.16, 7.0, 7.0.0.1, 7.0.0.2, 7.0.0.3, 7.0.0.4, 7.0.1, 7.0.1.1, 7.0.1.2, 7.0.1.3, 7.0.2

Operating system(s):
AIX, HP-UX, Solaris, Windows, Linux

Document number:
332717

Modified date:
16 June 2018

UID

swg21146114

Page Feedback