JDK-5010244 : PSARC/2003/321 needs to be backported to 1.4.2_05
  • Type: Bug
  • Component: tools
  • Sub-Component: launcher
  • Affected Version: solaris_10,1.4.2,1.4.2_05
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_8,solaris_9,solaris_10
  • CPU: generic,sparc
  • Submitted: 2004-03-09
  • Updated: 2017-05-16
  • Resolved: 2004-05-10
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_05 05Fixed
Related Reports
Duplicate :  
JDK-5049912 - JDK 1.5.0 is not default in s10_58 (S10 beta4)
Relates :  
JDK-5047507 - javaws not correctly maintained in 1.4.2_05 b2 (internal)
Relates :  
JDK-6359688 - Zip API classes do not report name of file when it cannot be opened
Description
As described in PSARC/2003/321, the Multiple JRE support is intended
to be backported to the tail of appropriate release series.  At a
minimum, this must include the 1.4.2 family (others were optional
based upon business need - no such need has yet be cited).

It is very significant that the critically important 1.4.2 family
is the only Java release family which won't function as the final
target of a JRE release specification.  This is because a bug was
introduced in the support of the 32/64 bit version switching flags
which causes the launcher executable to not properly recognize
itself on Solaris and Linux.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.4.2_05 generic FIXED IN: 1.4.2_05 INTEGRATED IN: 1.4.2_05 VERIFIED IN: 1.4.2_05
18-06-2004
EVALUATION ###@###.### 2004-03-09 As per comments. The "self recognition" problem in the 1.4.2 launcher needs to be fixed and the Multiple JRE functionality also needs to be released. The safest (and simlest) way to do this is to backport the 1.5 launcher prior to the Kessler's automatic scaling changes. Note that this is introducing a new CLI/API in a patch release. Although exceptional in the j2se product, this has been approved by the j2se PAC and PSARC (and presented to the Solaris PAC without objection - its not clear thay had approval authority).
18-06-2004
SUGGESTED FIX ###@###.### 2004-03-09 The best way to address these two failures is to backport the 1.5 launcher (prior to the "automatic tuning" updates to 1.4.2. The changes related to factors other than these two failures are minimal and simple (such as renaming global data to avoid namespace conflicts). This has the advantage of cleanly leveraging the 1.5 testing and Beta exposure. Is this a "bug" or an "rfe"? The backport of 2003/321 is on the edge, quite possibly an rfe. The inability of the 1.4.2 launcher to correctly identify itself is clearly a bug.
18-06-2004
PUBLIC COMMENTS Internal development tracking report.
18-06-2004