-
Bug
-
Resolution: Fixed
-
P2
-
8u40, 9
-
b20
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8067979 | 9 | William Harnois | P2 | Closed | Fixed | b48 |
JDK-8083786 | emb-9 | William Harnois | P2 | Resolved | Fixed | team |
JDK-8071205 | 8u60 | William Harnois | P2 | Closed | Fixed | b01 |
JDK-8068475 | 8u45 | William Harnois | P2 | Closed | Fixed | b03 |
JDK-8069774 | emb-8u47 | William Harnois | P2 | Resolved | Fixed | team |
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.
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.
- backported by
-
JDK-8069774 RegisterDeploy ping not working correctly
- Resolved
-
JDK-8083786 RegisterDeploy ping not working correctly
- Resolved
-
JDK-8067979 RegisterDeploy ping not working correctly
- Closed
-
JDK-8068475 RegisterDeploy ping not working correctly
- Closed
-
JDK-8071205 RegisterDeploy ping not working correctly
- Closed