OCSP checks introduce speed penality when using lazy loading jars in jnlp

XMLWordPrintable

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: P3
    • None
    • Affects Version/s: 7u45
    • Component/s: deploy

      FULL PRODUCT VERSION :
      java version "1.7.0_45"
      Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
      Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)

      ADDITIONAL OS VERSION INFORMATION :
      Windows 7

      A DESCRIPTION OF THE PROBLEM :
      We use a jnlp file with one main jar and a lot of other jars that are lazy loaded. During startup for each jar and each CA in the certificate chain one OCSP requests is sent. This leads to a slow startup behaviour. If we do not use lazy loading only the certificate of the main jar is verified with OCSP as described in https://bugs.openjdk.java.net/browse/JDK-8023808.

      Since all the jars are signed using the same certificate the OCSP responses could be cached.


      REPRODUCIBILITY :
      This bug can be reproduced always.

            Assignee:
            Victor Drozdov (Inactive)
            Reporter:
            Webbug Group
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: