JDK-4890014 : reload button in IE reloads a new classlaoder even if other applets are using it
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 1.4.1
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2003-07-14
  • Updated: 2004-02-22
  • Resolved: 2003-08-07
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.
Other Other
1.4.1_07 07Fixed 1.4.2_02Fixed
Description
If we have 2 or more applets running in 2 or more IE browsers from the same 
source base and press reload in one of the browsers it reloads a new classloader
even though the old classloader was being used by the other applet(s).

Similar to bugId 4873484, but not the same. In this case we have multiple 
applets.

Attached testcase.zip demonstrates the problem.

###@###.### 2003-07-14
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.4.1_07 1.4.2_02 generic tiger-beta2 FIXED IN: 1.4.1_07 1.4.2_02 tiger-beta2 INTEGRATED IN: 1.4.1_07 1.4.2_02 tiger-beta2 VERIFIED IN: 1.4.1_07 1.4.2_02
14-06-2004
SUGGESTED FIX ClassLoaderInfo.java: public static synchronized void markNotCachable(...) < if(cli != null) { >if(cli != null && cli.references <= 1) { > /* references <= 1, beccause removeReference is called > after AppletViewer.preRefresh */ ###@###.### 2003-07-14
14-07-2003
EVALUATION If the ClassLoaderInfo instance is being references by another applet then we cannot simply destroy it. ###@###.### 2003-07-14
14-07-2003