United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-4904444 Applets requiring plugin 1.3.1 are unviewable after installing 1.4.2
JDK-4904444 : Applets requiring plugin 1.3.1 are unviewable after installing 1.4.2

Details
Type:
Bug
Submit Date:
2003-08-11
Status:
Closed
Updated Date:
2004-01-07
Project Name:
JDK
Resolved Date:
2003-09-30
Component:
deploy
OS:
windows_nt,windows_xp,windows_2000
Sub-Component:
plugin
CPU:
x86,generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
1.3.1,1.4.1,1.4.2,1.4.2_01,1.4.2_02
Fixed Versions:
1.4.2_04 (04)

Related Reports
Backport:
Duplicate:
Duplicate:
Relates:

Sub Tasks

Description
Name: gm110360			Date: 08/11/2003


FULL PRODUCT VERSION :
java version "1.4.2-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-beta-b19)
Java HotSpot(TM) Client VM (build 1.4.2-beta-b19, mixed mode)

FULL OS VERSION :
Windows 98 Version [4.10.2222]
Windows NT Version 4.0
Windows XP Version [5.1.2600]

Suspect any WinX version.

EXTRA RELEVANT SYSTEM CONFIGURATION :
Internet Explorer Version 6.0.2600.0000

Installed JREs:
1.3.1_08
1.4.2-beta

A DESCRIPTION OF THE PROBLEM :
When Java plug-in version 1.3.1_xx is installed on a system that also has Java Plug-in version 1.4.2-beta, applets using 1.3.1_xx are not displayed correctly.

When an OBJECT tag is used to force an applet to run under Java Plug-in version 1.3.1_xx on a Windows client, the applet appears in a small box in the upper left corner of Internet Explorer if JRE 1.4.2-beta was also installed on the same client computer. The applet appears to hang until the mouse cursor is positioned over it, at which point tghe applet runs. However, the applet is still unusuable because all GUI components are 'squished' into the small box mentioned.

Resizing the IE window and reloaded/refreshing the web page do not help. Uninstalling JRE 1.4.2-beta does not resolve the problem either. The only resolution is to actually eliminate the problem by not installing JRE 1.4.2-beta on the same client as long as there is a need to run 1.3.1_xx applets.





STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1) Download and install JRE 1.3.1_06
2) Download and install J2SDK 1.4.2-beta (it doesn't matter if you install the SDK as well as long as the Runtime Environment is installed)
3) Create an HTML page called 'blink13106.html' with the folling source code:
<HTML>
<HEAD>
<TITLE>Blink Using 1.3.1_06</title>
</head>
<BODY>
<OBJECT ID='Blink' classid='clsid:CAFEEFAC-0013-0001-0006-ABCDEFFEDCBA' codebase='http://java.sun.com/products/plugin/1.3/jinstall-13-win32.cab#Version=1,3,1,6'>
<PARAM NAME = CODE VALUE = "Blink.class">
<param name=lbl value="This is the next best thing to sliced bread! Toast, toast, toast, butter, jam, toast, marmite, toast.">
<param name=speed value="4">
</object>
</body>
</html>

4) Save the page create in (3) in the same folder as the blink.class demo applet that comes with the SDK.

5) Create another HTML page called 'blink142.html' with the following source:
<HTML>
<HEAD>
<TITLE>Blink using 1.4.2-beta</title>
</head>
<BODY>
<OBJECT ID='Blink' classid='clsid:CAFEEFAC-0014-0002-0000-ABCDEFFEDCBA' codebase='http://java.sun.com/products/plugin/1.4/jinstall-14-win32.cab#Version=1,4,2'>
<PARAM NAME = CODE VALUE = 'Blink.class'>
<param name=lbl value="This is the next best thing to sliced bread! Toast, toast, toast, butter, jam, toast, marmite, toast.">
<param name=speed value="4">
</object>
</body>
</html>

6) Save the page created in (5) in the same folder as the blink.class demo applet that comes with the SDK.

7) From the Windows Explorer, double-click on blink142.html. The Java Plug-in version 1.4.2 is loaded and runs the applet.

8) Close the web browser.

9) From Windows Explorer, double-click on blink13106.html. The Java Plug-in version 1.3.1_06 is loaded but the applet appears in a small unviewable box in the upper left corner of the Internet Explorer window.



EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
After double-clicking the blink13106.html, Java Plug-in 1.3.1_06 should have started the demo applet and the applet should have run normally.
ACTUAL -
The applet appears in a small window in the upper left corner of the Internet Explorer window. The applet is essentially unusable. Also, the applet appears to hang (or IE appears to keep loading something) until the mouse cursor is moved over the applet at which point, the applet runs but is still unusable.

ERROR MESSAGES/STACK TRACES THAT OCCUR :
No errors are reported.

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :
No workarounds. You must uninstall all JREs and then re-install the desired Java 1.3.1_xx version in order to get applets requiring that version to function.
(Incident Review ID: 187157) 
======================================================================
###@###.### 2003-08-28

                                    

Comments
WORK AROUND

Suggested workaround:
================
Until better workaround or solution is available, here is the suggested workaround (based on scenario 5):
If 1.3.1_0X must co-exist with other later JRE version(s), make sure it's installed LAST.
###@###.### 2003-08-28

===================================================================
the problem was caused because of several registries required for
1.3.1_X to operate are missing.  These registries were removed when 1.4.2 
or later JRE is installed on your system
after installation of 1.3.1_X.  They are:

HKEY_LOCAL_MACHINE
   ->SOFTWARE
      ->Classes
         ->CLSID
            ->{8AD9C840-044E-11D1-B3E9-00805F499D93}
               ->MiscStatus (Name=(Default), Type=REG_SZ, Data=0)
                  ->1 (Name=(Default), Type=REG_SZ, Data=2449)

The workaround for Mantis is to manually add these registries or import the attached file "fix.reg" at
the HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{8AD9C840-044E-11D1-B3E9-00805F499D93}
location.
The real fix should go to tiger (1.5.0), where the installer should add these registries to make sure 1.5.0 is
backward compatible with 1.3.1_X.  Contacted JInstall engineer to make sure this fix go
into 1.5.0.
###@###.### 2003-09-03
                                     
2003-09-03
EVALUATION

Investigation result:
=============
This problem is reproduceable, where the order of installation of different versions of JRE
deems important.  Symptom can be described as:
If JRE 1.3.1_0X is installed before JRE 1.4.2 or later (tiger), running applet that specifies
to make use ONLY of 1.3.1_0X on Internet Explorer on MS Windows (XP, have not
tested on other Windows platform) will:

(1) Applet won't load until mouse cursor is moved over the applet's frame.
(2) Applet frame size (WIDTH & HEIGHT) specified is not realized by plugin.  The
frame is showed up with tiny width & height that is not usable.

Tested the following scenarios on WinXP:
(1) Installed JRE 1.3.1_04, 1.3.1_06, 1.3.1_09 (in that order).  For each, select it as
java runtime for IE browser at installation.  all applets that specify to use only
1.3.1_04, or 1.3.1_06, or 1.3.1_09 work fine.
(2) Installed JRE 1.4.2 after scenario (1).  Whether select or unselect it as java runtime
for IE browser during installation.   All applets that specify to use only 1.3.1_0X exhibit
the afore-mentioned problem.
(3) Installed JRE 1.5.0 beta after (1) and (2).  Still the same problem with all applets that
specify to use only 1.3.1_0X.  But applet that makes use only of 1.4.2 works fine.
(4) Uninstalled all JREs installed in (1), (2) & (3).  Reinstalled JRE 1.3.1_06, then installed
JRE 1.5.0 (beta), same problem as in (2).
(5) Uninstalled then reinstalled JRE 1.3.1_06.  All WORK fine!
(6) Uninstalled all JREs on the machine.  Installed only 1.3.1_09 JRE with IE browser
_DESELECT_ during installation.  After installation, open 1.3.1_09's Java Control Panel to select
java runtime as default for IE.  None of the applet works!  All applets exhibit the same
reported problem.
(7) Uninstalled JRE 1.3.1_09 then reinstalled it again.  This time, select IE browser AT installation.
All applets work again!

The problem is not with Netscape browser on WinXP.

Suggested problem root cost:
====================
The problem seems to be related to registry settings in reference to IE browser.  Certain registry
entries required by JRE 1.3.1_0X may be overridden or removed when installing 1.4.2 or later.
Scenarios (6) & (7) are very interesting and may suggest that problem has started to occur with
1.3.1_09.

Suggested workaround:
================
Until better workaround or solution is available, here is the suggested workaround (based on scenario 5):
If 1.3.1_0X must co-exist with other later JRE version(s), make sure it's installed LAST.

(by ###@###.###)
###@###.### 2003-08-28

==========================================================================================
the problem was caused because of several registries required for
1.3.1_X to operate are missing.  These registries were removed when 1.4.2 
or later JRE is installed on your system
after installation of 1.3.1_X.  They are:

HKEY_LOCAL_MACHINE
   ->SOFTWARE
      ->Classes
         ->CLSID
            ->{8AD9C840-044E-11D1-B3E9-00805F499D93}
               ->MiscStatus (Name=(Default), Type=REG_SZ, Data=0)
                  ->1 (Name=(Default), Type=REG_SZ, Data=2449)

The workaround for Mantis is to manually add these registries or import the attached file "fix.reg" at
the HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{8AD9C840-044E-11D1-B3E9-00805F499D93}
location.
The real fix should go to tiger (1.5.0), where the installer should add these registries to make sure 1.5.0 is
backward compatible with 1.3.1_X.  Contacted JInstall engineer to make sure this fix go
into 1.5.0.

###@###.### 2003-09-03
                                     
2003-09-03
SUGGESTED FIX

Suggested problem root cost:
====================
The problem seems to be related to registry settings in reference to IE browser.  Certain registry
entries required by JRE 1.3.1_0X may be overridden or removed when installing 1.4.2 or later.
Scenarios (6) & (7) are very interesting and may suggest that problem has started to occur with
1.3.1_09.

===============================================
The real fix should go to tiger (1.5.0), where the installer should add these registries to make sure 1.5.0 is
backward compatible with 1.3.1_X.  Contacted JInstall engineer to make sure this fix go
into 1.5.0.
###@###.### 2003-08-28
###@###.### 2003-09-03

###@###.### 2003-09-24

1.4.2_02 will have following fix

------- RegCurrentVersion.rgs -------
*** /tmp/sccs.3Aayof    Wed Sep 24 11:04:09 2003
--- RegCurrentVersion.rgs       Wed Sep 24 11:09:45 2003
***************
*** 24,29 ****
--- 24,35 ----
            {
                val ThreadingModel = s 'Apartment'
            }
+           ForceRemove 'MiscStatus' = s '0'
+           {
+               ForceRemove '1' = s '2449'
+               {
+               }
+           }
        }
      }
                                     
2004-06-11
CONVERTED DATA

BugTraq+ Release Management Values

COMMIT TO FIX:
1.4.2_04
tiger

FIXED IN:
1.4.2_04
tiger

INTEGRATED IN:
1.4.2_04
tiger
tiger-b22

VERIFIED IN:
1.4.2_04


                                     
2004-06-14



Hardware and Software, Engineered to Work Together