JDK-6261009 : Loading 1.5 plugin from HTTPS page fails for W2K3 user with mandatory profile
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 5.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2005-04-25
  • Updated: 2010-04-04
  • Resolved: 2005-08-31
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 6
6 b50Fixed
Related Reports
Relates :  
Description
FULL PRODUCT VERSION :
java version "1.5.0_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_02-b09)
Java HotSpot(TM) Client VM (build 1.5.0_02-b09, mixed mode)

ADDITIONAL OS VERSION INFORMATION :
Windows2K3 Server
Microsoft Windows [Version 5.2.3790]


A DESCRIPTION OF THE PROBLEM :
see BugID: 4774627
Problems trying to load an applet from an https web page when using the mandatory profiles on Windows 2003 (ntuser.man) instead of the typical profiles (ntuser.dat).
This bug 4774627 has been closed and fixed. It seems I hit this bug again with Windows2003 users with mandatory profiles.

Here the display of the Java console of a Windows2003 user in a mandatory profile (Ntuser.man):
Java Plug-in 1.5.0_02
Using JRE version 1.5.0_02 Java HotSpot(TM) Client VM
User home directory = C:\Documents and Settings\ZIVACO01
----------------------------------------------------
c:   clear console window
f:   finalize objects on finalization queue
g:   garbage collect
h:   display this help message
l:   dump classloader list
m:   print memory usage
o:   trigger logging
p:   reload proxy configuration
q:   hide console
r:   reload policy configuration
s:   dump system and deployment properties
t:   dump thread list
v:   dump thread stack
x:   clear classloader cache
0-5: set trace level to <n>
----------------------------------------------------
Trace level set to 5: all ... completed.
basic: Registered modality listener
liveconnect: Invoking JS method: document
liveconnect: Invoking JS method: URL
basic: null

Here is the display of the java console of a Windows2003 user with a typical or roaming profile (Ntuser.dat):
Java Plug-in 1.5.0_02
Using JRE version 1.5.0_02 Java HotSpot(TM) Client VM
User home directory = C:\Documents and Settings\ZIVACO01
----------------------------------------------------
c:   clear console window
f:   finalize objects on finalization queue
g:   garbage collect
h:   display this help message
l:   dump classloader list
m:   print memory usage
o:   trigger logging
p:   reload proxy configuration
q:   hide console
r:   reload policy configuration
s:   dump system and deployment properties
t:   dump thread list
v:   dump thread stack
x:   clear classloader cache
0-5: set trace level to <n>
----------------------------------------------------
Trace level set to 5: all ... completed.
basic: Registered modality listener
liveconnect: Invoking JS method: document
liveconnect: Invoking JS method: URL
basic: Referencing classloader: sun.plugin.ClassLoaderInfo@e29820, refcount=1
basic: Added progress listener: sun.plugin.util.GrayBoxPainter@1d6fbb3
basic: Loading applet ...
basic: Initializing applet ...
basic: Starting applet ...

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
with a user on Windows2003 Terminal Server with mandatory profile, connect to https://www4.rbc.com/nj00-wcm

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Applet should be loaded
ACTUAL -
Applet is not loaded and the login process cannot be done

ERROR MESSAGES/STACK TRACES THAT OCCUR :
No errors appear. But if the user tried to log in and the applet is not loaded, Internet Explorer cannot no more be closed normally. Task Manager must be started to end the Internet Explorer process.

REPRODUCIBILITY :
This bug can be reproduced always.
###@###.### 2005-04-25 21:49:52 GMT

Comments
EVALUATION This problem is already fixed in the current 1.5.x build. The fix will be put into Mustang as well.
15-08-2005

SUGGESTED FIX webrev: http://web-east.east/www/webrevs/aw158418/6261009/webrev testcase: http://web-east.east/www/tests/1.6.0/6261009
15-08-2005