JDK-7015081 : Need to make sure upgrader status stored in the some form of registry not in the old cache dir.
- Type: Bug
- Component: deploy
- Sub-Component: deployment_toolkit
- Affected Version: 7
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2011-01-26
- Updated: 2016-04-20
- Resolved: 2011-03-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.
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 b130Fixed  |
Related Reports
|
Relates :
|
Description
We save upgrade status in the old cache dir. This is potentially problematic - what if upgrade is "in progress" from multiple hosts simultaneously and these hosts have dynamic IPs? What if this old dir is read only and we can not save status there? What if this old dir is "slow" (not sure if roaming profile supports "copy on demand"), then check may become very expensive and we are doing it forever. (igor) I think we better use registry for this as upgrade it windows only.
Comments
|