JDK-7172340 : PIT 8(b41) Reinstall test JDK/JRE over test JDK failed
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 8
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows
  • CPU: x86
  • Submitted: 2012-05-29
  • Updated: 2013-11-12
  • Resolved: 2013-11-12
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.
JDK 8
8-poolResolved
Related Reports
Relates :  
JDK-6831192 - running installer wrappers 2 times creates bad UE
Description
reproduced steps:
1.invoke JDK installer. Select development tools and Source Code,deSelect Public JRE.
 or install silently with "/s /v/qn ADDLOCAL=ToolsFeature,SourceFeature JDKONLY=TRUE"
2.launch JDK installer again.Confirm YES to reinstall JDK.Go through installation with default setting.
  or install silently with "/s /v/qn  JDKONLY=TRUE"
3.if install not silently,
  can see error dialog appeared,with infomation "Error 1335.The cabinet file 'st180000.cab' required for this installation is corrup and cannot be used.This could indicate a network error,an error reading from the CD-ROM,or a problem with this package."
  if install silently,
  Expected: JRE is installed sucessfully.
  Actual: JRE is not there.
both 32 bit bundle and 64 bit bundle jdk180.exe have this issue
Comments
This issue is now fixed with JDK/JRE reinstall redesign fixes. Here are the JRE and JDK reinstall redesign change-sets: URL: http://closedjdk.us.oracle.com/jdk8/jdk8/install/rev/014392ee2ceb User: jqzuo Date: 2013-10-22 22:56:25 +0000 URL: http://closedjdk.us.oracle.com/jdk8/jdk8/install/rev/99c9c25dd84d User: jqzuo Date: 2013-11-12 18:19:33 +0000
12-11-2013
EVALUATION The issue would be that the first install does not completely finish yet. The second install starts. Since the install files from the first install may not be deleted yet, you try to extract the files for the second install, you will get the error. I do not think this applies to the real world since why the user needs to run the same install twice in a row. Lower the priority to p4. For the automation testing, the issue can be resolved by setting the wait time between the two installations. Please also remove the JDKONLY=TRUE flag as it does not apply anymore since there is no more jdk/sdk co-bundle installer in jdk8 now.
29-05-2012