JDK-5012380 : Java Plugin clean up thread uses 50Mb as limit even though unlimited is used
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 1.4.2_03
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2004-03-12
  • Updated: 2004-04-28
  • Resolved: 2004-04-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.
1.4.2_05 05Fixed
OS: Windows 2000
Product: JRE 1.4.2_03

Files in PlugIn cache are deleted on machine with a lot available memory and unlimited
cache size. It seems that the cleaner thread uses 50M for limitation and ignores the actual setting.
It happens on JRE1.4.2_02 and 1.4.2_03.

Test case
The problem occurs as a result of having the Cache Details Window from the Java 
Plug-in Control Panel open for more than a minute.  Here are the steps:

1) Close all instances of the Java Plug-in Control Panel.
2) Navigate an URL to install 100+ MB of JARs:  
3) Open the Java Plug-in Control Panel.
4) Select the Cache Tab and click View, leave it open.
5) After 1 minute the cache will be reduced to less than 50 MB.
###@###.### 2004-03-12
###@###.### 2004-03-12

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.4.2_05 generic FIXED IN: 1.4.2_05 INTEGRATED IN: 1.4.2_05 VERIFIED IN: 1.4.2_05

EVALUATION The root cause of the bug is caused by the Cache cleanup thread is controlled by reading the system property value java.plugin.size. After the Control Panel reads it from deployment.property file, it has never been set. So cache cleanup thread will run even though the size was set to "unlimited". This bug is not applied to tiger since tiger uses different way to handle the property. ###@###.### 2004-03-12

SUGGESTED FIX In src\plugin\share\classes\sun\plugin\panel\ConfigurationInfo.java, add java.net.Security.setProperty("javaplugin.cache.size", cacheSize); after cacheSize = props.getProperty("javaplugin.cache.size", "50m"); ###@###.### 2004-03-12