JDK-6899834 : (launcher) remove the solaris libjvm.so symlink
- Type: Bug
- Component: tools
- Sub-Component: launcher
- Affected Version: 7
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2009-11-10
- Updated: 2017-05-16
- Resolved: 2011-07-15
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.
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.
| JDK 7 |
|---|
7 b78Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
Solaris version of the JRE has a symlink in jre/lib/$os.arch/libjvm.so -> client/libjvm.so, this was added in the early days of Java to maintain backward compatibility with the earlier versions. This symlink has been problematic in the past as it loads both the server and the client libjvm.so simultaneously. These problems were circumvented by setting the LD_LIBRARY_PATH by the launcher to the flavor of the libjvm.so to be loaded (server/client). With the purging of the LD_LIBRARY_PATH setting in the launcher see 6367077, this will no longer be the case and the previous issues will be exposed, therefore this symlink needs to be removed now.
Comments
|