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

Applet Persistence API is broken in the next-generation plugin

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • P3
    • 7
    • 6u22
    • deploy
    • x86
    • windows_xp

    Description

      FULL PRODUCT VERSION :
      java version "1.6.0_22"
      Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
      Java HotSpot(TM) Client VM (build 17.1-b03, mixed mode, sharing)

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

      A DESCRIPTION OF THE PROBLEM :
      The plugin developer guide section of the current Java SE Documentation states:

      "Beginning with JDK 1.4, two new methods have been added to interface
      java.Applet.AppletContext to allow applet persistence across browser sessions."

      - AppletContext.setStream
      - AppletContext.getStream

      It appears that this functionality stopped working in the next-generation java-plugin. The new plugin has the ability to stop and start an attached JVM. When a JVM is stopped, all date stored with the Applet Persistence API is lost.

      This is a regression bug.

      STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
      Preparations: two simple Applets using the same Codebase. One applet should store data using the Applet Persistence API and the other applet should read that data (and write it to the java console for example..).

      1. Store data using the setStream-Method of the Applet Persistence API
      2. Wait about one minute until the JVM is stopped by the java plugin (the java icon disappears from the windows system tray and the java console window is closed).
      3. Read data using the getStream-Method.

      EXPECTED VERSUS ACTUAL BEHAVIOR :
      EXPECTED -
      The data which was stored using setStream is returned.

      This happens when you do NOT wait in step 2 or when you use the classic plugin.
      ACTUAL -
      No data is returned.


      REPRODUCIBILITY :
      This bug can be reproduced always.

      CUSTOMER SUBMITTED WORKAROUND :
      This is a regression bug. It worked fine including Java 6 Update 07.

      Release Regression From : 6u7
      The above release value was the last known release where this
      bug was not reproducible. Since then there has been a regression.

      Attachments

        Issue Links

          Activity

            People

              henryjen Henry Jen
              ndcosta Nelson Dcosta (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: