Troubleshooting
Problem
When you run a java client application from client host, you may encounter the following console output error : java.lang.UnsatisfiedLinkError: The Symphony API could not complete its static initialization because it was unable to load some of its dependencies. An attempt was made to load both the 32-bit version (jnativesoamapi_7.1.0) and the 64-bit version (jnativesoamapi_7.1.0_64) of its dependent libraries. In most cases, failure to load both of these libraries is a symptom of an incorrectly configured environment. Ensure your environment is configured correctly. Cause: java.lang. UnsatisfiedLinkError: D:\IBM\Sym71Compute\soam\7.1\w2k3_x64-vc7- psdk\lib64\jnativesoamapi_7.1.0_64.dll: The operating system cannot run %1 Therefore, the java client stops running and exits.
Symptom
When running java client application, the client initially tries to load the dependency libraries of jnativesoamapi_7.1.0, but it fails at some point.
Cause
jnativesoamapi_7.1.0 is Symphony's bulit-in jnative SOAM library. It has many dependency libraries to be loaded from Symphony's lib directories. If one dependency library is loaded from the system library directory (e.g. from C:\Windows\System32\) instead, then this error may occur because the version of loaded library may not be correct or too old.
Environment
Windows client host who submits workload to the cluster.
Diagnosing The Problem
In order to diagnose the problem in detail, use the Microsoft Sysinternals Process Monitor tool. Use it to profile library load calls in real time when you run your Java client to see if a dependency library is loaded from an inappropriate directory.
Resolving The Problem
Uninstall the incorrectly loaded library so that the correct library from the Symphony installation can be loaded. If this is not possible due to other software dependancies, see if it can be replaced by Symphony's version.
Was this topic helpful?
Document Information
Modified date:
23 June 2018
UID
isg3T1026016