FULL PRODUCT VERSION :
java version "1.8.0_102"
Java(TM) SE Runtime Environment (build 1.8.0_102-b14)
Java HotSpot(TM) Client VM (build 25.102-b14, mixed mode, sharing)

ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows [versie 6.1.7601]

A DESCRIPTION OF THE PROBLEM :
Hi,

we have a big webstart application (370 jars, 450MB in size). When the webstart cache contains all the jars, starting this application using webstart 1.8.0_102 takes about 35 seconds before our main class gets executed. When we start the same application using webstart 1.8.0_25, it only takes about 7 seconds.

We did some profiling of the startup process and noticed a big difference between 1.8.0_102 and 1.8.0_25 in the com.sun.deploy.cache.CacheEntry 'getJarSigningData' method. We have the impression that 1.8.0_25 reads the signing information directly from the cached idx-file, while 1.8.0_102 always seems to scans the whole cached jar files to extract this information from.

REGRESSION. Last worked in version 8u77

ADDITIONAL REGRESSION INFORMATION:
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b18)
Java HotSpot(TM) Client VM (build 25.25-b02, mixed mode, sharing)

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
The application starts within a few seconds.
ACTUAL -
The application starts after 35 seconds.

REPRODUCIBILITY :
This bug can be reproduced always.