JDK-6570373 : download error handling in java kernel
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 6u4
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows
  • CPU: x86
  • Submitted: 2007-06-15
  • Updated: 2010-04-04
  • Resolved: 2008-04-08
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 6
6u10Resolved
Related Reports
Duplicate :  
Description
we need to make sure we handle all the download error cases below:

Unable to contact server
Unexpected error from server
Can't communicate with proxy
Remote I/O error while downloading - A network I/O error, as opposed to an I/O error on the local filesystem.
Local I/O error while downloading Disk full
Checksum verification failed
Downloaded file is already present, but the two files are not the same -- overwrite or cancel?
when poping up error dialog, we need to make sure it will be a top level modal dialog, so user will be able to see it and response to it:

    For a while I was going through line 1062 of the DownloadDialog.cpp code where  it puts out a dialog with error  IDS_HTTP_STATUS_EXPORT_FAILURE. I was very confused about being told I was in an embargoed country and then tracked it back to HTTP error 403, which was telling me my bundle directory path permissions were messaged up (one directory had perms  770). I suspect this is standard behavior, but wanted to pass it along.
   However the major reason I'm sending this msg is that when this dialog is put up it ends up behind the download dialog. So for a while I couldn't figure out what was happening but something led me to find the dialog reporting the msg above and waiting for an "OK." I think this will give users problems if it happens in any "normal" circumstance.

Comments
EVALUATION this is already addressed by: 6644778: Improve handling of failed bundle downloads
08-04-2008