ed03875

What we are seeing is that the JVM only looks for library files where the jvm is being loaded from and never searches the LD_LIBRARY_PATH in the example above the...

Please see below where we are now using 8u322, I fell I am either missing something very basic here (note: the J9 JVM works in this configuration) or the Hotspot...

cat /etc/os-release NAME="CentOS Linux" VERSION="7 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="7" PRETTY_NAME="CentOS Linux 7 (Core)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:7" HOME_URL="[https://www.centos.org/"](https://www.centos.org/%22) BUG_REPORT_URL="[https://bugs.centos.org/"](https://bugs.centos.org/%22) CENTOS_MANTISBT_PROJECT="CentOS-7" CENTOS_MANTISBT_PROJECT_VERSION="7" REDHAT_SUPPORT_PRODUCT="centos" REDHAT_SUPPORT_PRODUCT_VERSION="7"

One thing that may not have been clear is this problem of ignoring the LD_LIBRARY_PATH and -Djava.library.path happens when we load libjvm.so programmatically

We load the JVM in a very standard way res = JNI_CreateJavaVM(&jvm, (void**)&env, &vm_args) This is published in many places.

I wish it was that easy. We believe we are setting the Library path see below. The JVM should be able to find libjava.so in the library path here bin/linux64/bin/jvm/lib/amd64:...

This is the path to our jre directory equivalent /home/mkarra/sandboxes/hotspotjdk/bin/linux64/bin/ this is the jre directory for our product jvm/ this is the the directory where libjava.so resides lib/amd64 So you...

Windows 64 works because all the shared objects are in the bin area With Linux the shared objects are in the lib/amd64 directory for AIX it is similar Hotspot looks...

Unfortunately we had to give up on the port of our products to HotSpot. There are to many unresolved issues and the HotSpot port to AIX seems incomplete