Summary: | Update test R2, Connection time out | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Konrad Kolosowski <konradk> | ||||
Component: | Update (deprecated - use Eclipse>Equinox>p2) | Assignee: | Christophe Elek <celek> | ||||
Status: | RESOLVED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | jeem | ||||
Version: | 2.0.2 | ||||||
Target Milestone: | 2.0.2 | ||||||
Hardware: | Sun | ||||||
OS: | Solaris | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Konrad Kolosowski
2002-10-10 14:16:51 EDT
Created attachment 2156 [details]
timeout error dialog.gif
we need to only map fully downloaded jar alternativley we need to check if the JAR has changed on the server investigate getTimeStamp() getLastModified() getContentLenght() from URLConnection() class If 'lastModified' on server is the same as the one in temp, but content length is not, we should make assumption that the local copy is currupted. Alternatively, we delete the local copy if download is not successful. investigate for 2.0.2 Will do for 2.0.2 refactored the methods Utilities.createLocalFile() and JarContentReference.unpack() Utilities now contains 2 methods createLocalFile() actually creates the file but does not map it mapLocalFile() maps the local file to the key unpack now calls createLocalFile and mapLocalFile when the download has been successfull So, when this issue happens, restarting the install will download the JAR again instead of attempting to use the one downloaded. Great. What about the first error (Connection time out)? I thought the files were available on my local machine, so I would not expect time out? The error is a valid error returned by the server when opening the stream. Anything could have happen as I seem to remember the AIX/HP-UX and other are not physically in the same lab as the site. A firewall or a router could have caused this *** Bug 20668 has been marked as a duplicate of this bug. *** |