JDK-4731671 : launcher sets runpath incorrectly on Solaris
  • Type: Bug
  • Component: tools
  • Sub-Component: launcher
  • Affected Version: 1.4.2
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris
  • CPU: generic
  • Submitted: 2002-08-14
  • Updated: 2010-02-01
  • Resolved: 2002-11-07
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.4.2 mantisFixed
Related Reports
Relates :  
JDK-6367077 - Purge LD_LIBRARY_PATH usage from the launcher
Relates :  
JDK-6254947 - java.library.path includes 32-bit usr/lib on 64-bit jvm
Relates :  
JDK-6312057 - 64 bit jvm is not looking at LD_LIBRARY_PATH_64 to find the JNI libraries
Description
On unix systems, the Java launcher examines LD_LIBRARY_PATH to determine if the runpath is set correctly to invoke java.  On Solaris, only examining LD_LIBRARY_PATH without examining LD_LIBRARY_PATH_32 and LD_LIBRARY_PATH_64 is incorrect since the data model specific variables, if set, override LD_LIBRARY_PATH.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mantis FIXED IN: mantis INTEGRATED IN: mantis mantis-b07
14-06-2004
SUGGESTED FIX Proper LD_LIBRARY_PATH* logic added; see Solaris-only code diffs listed in bug 4731666 for function SetLibraryPath in src/solaris/bin/java_md.c. ###@###.### 2002-11-07
07-11-2002
EVALUATION LD_LIBRARY_PATH variables on Solaris should be examined in the same order and priority as the dynamic linker, ld.so.1. ###@###.### 2002-08-14
14-08-2002