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

When applet is relaunched, extra JUT records can be sent

    XMLWordPrintable

Details

    • b01
    • Verified

    Backports

      Description

        This is a request from JAMC. See JAMC-1748 and JAMC-1595 for details, and also JEM-244 at https://javafx-jira.kenai.com/browse/JEM-244.

        A problem, in a few words. Suppose an applet requires Java version X. It is launched on a desktop with versions X and Y installed, and version Y is the current, used by Java Plugin / Web Start. The applet is first launched with version Y, then re-launched with version X in a new process. It results in two Java Usage Tracker records:

        plugin2, appName java_version=X, version Y
        plugin2, appName java_version=X __applet_relaunched, version X

        The problem here is that the applet was not actually run with version Y, as the first JUT record implies. Java Plugin / Web Start should not report any JUT records, until:

        1. It is clear what Java version is available and will be used to run the applet
        2. It is clear that user has not cancelled application run (e.g. pressed "Cancel" button in a warning dialog)

        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8078704 When applet is relaunched, extra JUT records can be sent

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8079924 When applet is relaunched, extra JUT records can be sent

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8082200 When applet is relaunched, extra JUT records can be sent

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8137452 When applet is relaunched, extra JUT records can be sent

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8078864 When applet is relaunched, extra JUT records can be sent

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8078872 When applet is relaunched, extra JUT records can be sent

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed

            Activity

              People

                herrick Andy Herrick (Inactive)
                art Artem Ananiev (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: