The following public summary may be used as a release note:
Solaris Hotspot VM java.library.path change: In previous releases, if the java.library.path property was not explicitly set, a Solaris Hotspot VM created by JNI_CreateJavaVM would in some cases incorrectly initialize the property. This behavior has been corrected in this release. The specific changes are as follows:
* Initialize java.library.path from the data model specific LD_LIBRARY_PATH_32 or LD_LIBRARY_PATH_64 if it's set, otherwise LD_LIBRARY_PATH.
* System crle(1) settings will be recognized.
* The 64-bit VM will now correctly append /usr/lib/64 to java.library.path instead of /usr/lib.
Except for the /usr/lib/64 change, these changes will only affect VMs created with JNI_CreateJavaVM. Applications created via the Java launcher will not be affected.
In very rare cases, applications that used incorrect LD_LIBRARY_PATH settings to work around this bug may need to adjust their environment to avoid UnsatisfiedLinkErrors loading native libraries. In this case, it is recommended to correct your LD_LIBRARY_PATH setting or to explicitly set java.library.path to the desired value.