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

RegisterDeploy ping not working correctly

    XMLWordPrintable

Details

    • b20
    • Verified

    Backports

      Description

        Installer.exe is no longer setting the RegDeployStatus registry after calling RegisterDeploy(). The purpose of this was to send a special evar42 ping to track the RegisterDeploy() pass %. It appears this stopped working correctly after the 8u20 msi redesign.

        When tracking 1603/1606 errors, it's good to know how many of them are a result of RegisterDeploy failing. I've seen a bunch of jusched.log's from customers that indicate that it's failing often. But we won't know the true percentage until this is fixed.

        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-8069774 RegisterDeploy ping not working correctly

            • 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-8083786 RegisterDeploy ping not working correctly

            • 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-8067979 RegisterDeploy ping not working correctly

            • 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-8068475 RegisterDeploy ping not working correctly

            • 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-8071205 RegisterDeploy ping not working correctly

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

            Activity

              People

                billyh William Harnois
                billyh William Harnois
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: