JDK-8037413 : 64bit JDK Install writes RuntimeLib regkey as 'client'
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 7u51
  • Priority: P3
  • Status: Resolved
  • Resolution: Duplicate
  • OS: windows_7
  • CPU: x86
  • Submitted: 2014-03-14
  • Updated: 2015-03-18
  • Resolved: 2014-03-18
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.
JDK 7
7u65Resolved
Related Reports
Relates :  
JDK-8075410 - Registry path for jvm.dll is set to client instead of server
Description
A user reported the following: 
"Java version: jdk-7u51-windows-x64

Browser: Internet Explorer
 
User agent strings: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.146 Safari/537.36

A description of the problem:
This is regarding jdk-7u51-windows-x64 installation on Window 7 64 bit. After installation of JDK kit in Windows 7 64 bit I discovered there is no client folder in <Drive>:\Program Files\Java\jre7\bin. Then I read thread , and I figured that  actually its directory structure according to
http://www.oracle.com/technetwork/java/javase/jre-7-readme-430162.html. Now question comes here, If we have only server directory then why are we having client entry in registry [Java Runtime Environment\1.7\RuntimeLib\ targeting folder in client jvm.dll]. I think this is a Bug. Kindly refer following link for more description http://stackoverflow.com/questions/22318204/no-client-in-c-program-files-java-jre7-bin-in-jdk-7u51-windows-x64."
Comments
Duplicated by JDK-7058601.
18-03-2014
For JDK7, the bug is here: http://opengrok.ie.oracle.com:8080/opengrok/xref/jdk7u-dev/install/make/installerdll/installerdll/src/installer/RegInstall.cpp#370 (RegInstall.cpp, line 370) 370 if (stricmp(lpszMinorVersion, "3") == 0) { 371 wsprintf(szVMDir, "hotspot"); 372 } else { 373 wsprintf(szVMDir, "client"); 374 } It checks if it's in the 1.3 family first. If so, it sets it to a "hotspot" dir. If not 1.3 family, it sets it to "client". It needs to check if the installer is 32 or 64-bit, and set to client or server respectively.
17-03-2014
Need to know the impact of setting RuntimeLlib incorrectly to determine release target. Setting for 7u65, assuming impact is 'medium'.
17-03-2014
Reproduced the issue: 1. Install 64bit JDK on Win7. 2. Regkeys written: HKLM/JavaSoft/Java Runtime Environment/1.7.0_51/RuntimeLib = "C:\Program Files\Java\jre7\bin\client\jvm.dll" HKLM/JavaSoft/Java Runtime Environment/1.7/RuntimeLib = "C:\Program Files\Java\jre7\bin\client\jvm.dll" Should be: "C:\Program Files\Java\jre7\bin\server\jvm.dll"
17-03-2014