Some adapters require access to Java libraries (.jar) and native libraries (.dll, .so, .dylib) which support the 3rd-party API. This is documented in each adapter section in the product Help.

When incorrectly configured, errors like this are seen:

[LogBack WARN] IP_RV_GNSS - Failed to create transport to 'RVD{service: '7500', network: '', daemon: 'tcp:7500'}': Library not found: tibrvj64
com.tibco.tibrv.TibrvException: Library not found: tibrvj64

This often means that the Java library (in this case tibrvj.jar) was found, but had a dependency on a native library which was not found on the PATH or library path.

Note: This article only applies to TIBCO StreamBase 7.x and prior. It does not apply to TIBCO Streaming 10.x or later.

Things to check and correct:

1. The API may require an environment variable to be set, like STREAMBASE_HOME, TIBCO_HOME, TIBRV_HOME. Check the product documentation for the necessary environment variables.

2. Update the PATH to have the integrated product's bin/ and lib/ directories present. For example, for TIBCO Rendezvous these directories may be needed on the path: /opt/tibco/tibrv/8.4/bin, /opt/tibco/tibrv/8.4/lib.

3. Check any other documented configuration steps. Sometimes the 3rd-party Java API library needs to be copied into the StreamBase server installation, or placed in a specific Operating System folder.

4. Check the permissions of the files and folders where the libraries are stored on the system. The file permissions may not permit the user account used for running the StreamBase server access to the required libraries. Correct the file permissions to allow access.
 

Causes and cures when the server does not find a required library.