JDK-8067251 : RegisterDeploy ping not working correctly
  • Type: Bug
  • Component: install
  • Affected Version: 8u40,9
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2014-12-11
  • Updated: 2018-01-11
  • Resolved: 2014-12-20
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
8u40 b20Fixed 9Fixed
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. 
Steps to reproduce error 1603: - Add/Set the env REGDEPLOY_INSTALL_DEBUG to "true". \ - Install the JUT - When you install, you'll see a message box pop up as it's about to call deploy.dll - delete the jre/bin/deploy.dll file and click ok to pop up The ping string generated for error 1603: INFO: Ping Values: $sc_xml_ver#1.0$reportsuiteid#suninstallstat$visitorid#82a093e7-54a7067f0$prop21#82a093e7-54a7067f0$prop20#XXXXXX$pagename#ic$evar42#2$evar24#0$evar25#0$evar2#1.8.0_40-ea-b21$evar15#1.8.0_40-ea-b21$evar40#-1$evar26#-99$evar27#$evar28#XX$evar4#i586$evar5#i586$evar6#win7-sp1$evar7#joff$evar8#US$events#event6,event7$evar17#1$evar18#YY$evar19#0$evar29#1$evar30#-1$evar31#32bit$evar33#XX$evar50#B11100$products#;jre|1603~32bit evar42 generated a non zero number Tested with 8u40 b21 PIT. Tested both offline / online installers.

After installation/upgrade, check the ping in jusched. The result of the RegDeploy API call should be pinged as evar42.

Bill/Paul, We need steps to reproduce the bug so we can verify the fix in the PIT.

8u40-critical-request justification: - Fix for Release : 8u40 - Justification : this is a regression in 8u20. jre|1603 is the highest reported error, and resolving this regression will allow us to triage and improve overall success rate of JRE installations. - Risk Analysis : low risk - reinstates logic previously in production - Webrev : https://java.se.oracle.com/code/cru/CR-JDK9CLIENT-650 - Testing (done/to-be-done) : dev tested for 8u40/8u40 PIT TBD, in production and working fine in 7u. - Back ports (done/to-be-done) : 9 only. 7 backports not required (working in 7). - FX Impact : NA