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

CLSID registry entries garbled after autoinstall JRE 1.5.0 through javaws if JRE 1.6.0_21 installed

    Details

    • Subcomponent:
    • CPU:
      x86
    • OS:
      windows

      Description

      Customer does have the requirement to run two javaws applications with different JRE concurrently. One of these two apps requires a JRE 1.5.0_11. Initially, when all was working fine, a JRE 1.6.0_07 was installed in parallel. Recently, customer went to JRE 1.6.0_21 and now experience the following symptom.

      Once the application that requires a JRE 1.5.0_11 autoinstall this JRE, the CLSID registry entries are garbled in the following way.. (notice the ^A where we usually refer to a DLL). The below is just an example of a garbled CLSID, all CLSIDs are garbled!

      :
      [HKEY_CURRENT_USER\Software\Classes\CLSID\{CAFEEFAC-0013-0001-0004-ABCDEFFEDCBA}\InprocServer32]
      @="^A"
      "ThreadingModel"="Apartment"
      :


      The ^A displays as a square in the registry as well as in IE (Tools > Manage Add-ons > Enable or Disable Add-ons > Show > Add-ons that have been used by IE). This is reproducible with the attached JNLP file.

      In order to recreate the symptom, install any recent JRE 1.6.0. I tried with JRE 1.6.0_15|21|22 with no difference. Then invoke the JNLP file manually. Note: The JNLP file sometimes has to be invoked multiple times to launch the JRE installer. Once the JRE 1.5.0 has been auto-installed, the CLSID registry entries are garbled.

      Being able to recreate the symptom, I observed the following things..

      - it's not specific to JRE 1.5.0_11, same does happen with any older/newer JRE 1.5.0 too
      - installing a JRE 1.5.0 the usual way in parallel does NOT trigger the symptom to happen
      - invoking the JRE installer manually does NOT trigger the symptom to happen

      In order to invoke the JRE installer manually, I picked the below CAB file and extracted the jinstaller.exe

      http://java.sun.com/update/1.5.0/jinstall-1_5_0_11-windows-i586.cab

      jinstall.exe /installurl=http://java.sun.com/update/1.5.0/1.5.0_11-b03.xml /installmethod=plugin


      - no difference when JRE 1.6.0 installed in patch-in-place or static mode
      - a toggle (enable or disable) of Java Plug-in through Java Control Panel seems to cure the registry


      So, the issue is really with autoinstall a JRE 1.5.0 if a more recent JRE 1.6.0 is already installed.

        Attachments

          Activity

            People

            • Assignee:
              vkarnauk Vladislav Karnaukhov
              Reporter:
              ohey Olaf Hey (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Imported:
                Indexed: