JDK-8144963 : Javaws checks jar files twice if JVM needs to be restarted
  • Type: Bug
  • Component: deploy
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2015-12-09
  • Updated: 2022-06-29
  • Resolved: 2015-12-15
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 7 JDK 8 JDK 9
7u101Fixed 8u101Fixed 9Fixed
Related Reports
Duplicate :  
JDK-8155912 - slow Java Webstart Application startup : possible performance problem in TrustDecider implementation
Description
After JDK-8052111 deployment doesn't store jar's signing data in cache as result javaws checks signing data twice if JVM needs to be restarted.
Comments
Discussed with Alex. Aiming to tidy up missing backports before RDP2 for 1603, or will defer.
19-04-2016
No issues found during PIT with 4 deploy fixes: http://st2.ru.oracle.com/StatusTool2/faces/queryresult2.jsp?matrix_id=1000031273 UR SQE OK to take it in CPU16_02
11-02-2016
Discussing the PIT options with Mikhail and Alex(P).
04-02-2016
The fix JDK-8144963 has been integrated in 8u74 b31 (BPR) with JDK-8133458. We faced with some troubles in the build. See JDK-8145712. So, we need all 3 fixes now: JDK-8133458, JDK-8145712 and JDK-8144963. Would better to have some kind of PIT with the build where all 3 fixes are integrated to make sure there are no more failures in this area. But we don't have time complete a such PIT before next build promotion. So, we may take a risk and take the fix to CPU16_02. At least no SQE OK.
04-02-2016
Critical Request - Justification: several customers faced with significant performance degradation in webstart application startup. 2 fixes were implemented to improve situation: JDK-8133458 and this one. JDK-8133458 was included to 8u75, we want to keep this fix and JDK-8133458 together. Customers expect to see them together in the same build, hence JDK-8144963 need to be included to 8u75 too. - Risk Analysis: Low - Webrev: https://java.se.oracle.com/code/cru/CR-JDK8UDEV-299 - Testing (done/to-be-done): turn on flight recorder and run jnlp that requires relaunch, without fix in both records you will that there're a lot of invocations of security.provider.SHA2.implCompress0(byte[], int), with fix, we checks all jars before relaunch only. - Back ports (done/to-be-done) : done to jdk7, will be done to jdk9 and maybe will be done to jdk6. - FX Impact: None - Fix For Release: 8u75
04-02-2016
setting the BPR Watch label as this fix is not reviewed in time for the current BPR slot. Watch will defer it to a later.
14-12-2015
This bug has no examples given of re-verification causing measurable performance degradation. I don't know if the proposed change at https://java.se.oracle.com/code/cru/CR-JDK8UDEV-299 will have any effect at all after 8144722 and 8140400 which attack the same problem in a simpler way, so such an example is required.
09-12-2015