Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-5086391

please refert back to 1.4.2 behaviour of checking changed jar files...

    XMLWordPrintable

    Details

    • Subcomponent:
    • Resolved In Build:
      01
    • CPU:
      x86
    • OS:
      windows_xp

      Backports

        Description



        Name: gm110360 Date: 08/12/2004


        FULL PRODUCT VERSION :
        java version "1.5.0-beta3"
        Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-beta3-b58)
        Java HotSpot(TM) Client VM (build 1.5.0-beta3-b58, mixed mode, sharing)

        ADDITIONAL OS VERSION INFORMATION :
        Microsoft Windows XP [Version 5.1.2600]

        A DESCRIPTION OF THE PROBLEM :
        in jdk1.4.2/webstart1.4.2 it was pretty perfect when using <offline-allowed/> in the jnlp to kickstart the app. It was the best performance enhancement i did in combination with giving the right timestamp to the jnlp files.

        Under 1.4.2 if the timestamp was still the same it jump started the application right from the cache. When the timestamp was different (the server was restarted ect) Then it did an extra check for the jars files BEFORE it kickstarted it. So if the jar also where changed it would download it before it would start the app.

        Now with 1.5 it is suddenly different. Even if the jnlp timestamp is changed it kickstarts the app anyway. But if the jars are then changed, i get a lot of errors. Because client and server are talking to each other (serialization).

        So PLEASE revert back to the 1.4.2 behaviour, because IF the jnlp file is changed then there is a big chance that there are more changes. Now i have to revert back to not using allowed offline at all. Which is very pitty...

        for pure performance this optimalisation we now have in 1.5.0 is minimal. The jnlp file timestamp should change that often anyway. !

        STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
        just make a webstart app and change the jnlp file, and you see it won't test the jars. Only the next time you boot. But then it is to late.


        EXPECTED VERSUS ACTUAL BEHAVIOR :
        EXPECTED -
        1.4.2 behaviour

        REPRODUCIBILITY :
        This bug can be reproduced always.

        CUSTOMER SUBMITTED WORKAROUND :
        don't use <offline-allowed/> anymore
        (Incident Review ID: 296408)
        ======================================================================

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                herrick Andy Herrick
                Reporter:
                gmanwanisunw Girish Manwani (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: