|
Quick Lists
|
|
Bug ID:
|
6533166
|
|
Votes
|
0
|
|
Synopsis
|
tzupdater 1.1.0 loops and takes a great deal of time to complete
|
|
Category
|
tzupdater:tool
|
|
Reported Against
|
|
|
Release Fixed
|
1.2.0(b01)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
1-Very High
|
|
Related Bugs
|
6535180
|
|
Submit Date
|
10-MAR-2007
|
|
Description
|
tzupdater is a critical tool to address DST issues with JRE. Previous versions of tzupdater could complete in a few minutes, with 1.1.0 we are seeing times in the 4-5 hour range due to looping through file systems. We are seeing several passes through each Java instance. We are seeing this on S10 and S9 machines.
Posted Date : 2007-03-10 09:54:28.0
see attachment "hollywood.txt" for another example of looping. This was reported by the softdist team. The process was terminated after one hour without completing.
Posted Date : 2007-03-22 17:23:49.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
The slow part we understand, I'm attaching a suggested fix which in my own tests improves package resolve time from 16 minutes to 4.
The looping part we have yet to assess: this could be just apparent looping due to the process being slow, or the find command. If the resolving script is processing the same JRE multiple times, then we can assess that further once we see a typescript.
Posted Date : 2007-03-15 15:37:53.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
