JDK-7011636 : Size of the cache is above the limit
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 7
  • Priority: P4
  • Status: Resolved
  • Resolution: Won't Fix
  • OS: windows
  • CPU: generic
  • Submitted: 2011-01-11
  • Updated: 2014-03-18
  • Resolved: 2014-03-18
Related Reports
Relates :  
JDK-6932885 - Java deployment cache size limit is not regarded
Description
This is to follow up on the fix for CR# 6932885 in jdk7.   It appears the fix failed when testing against jdk7-b125 PIT 

* Tested PIT bundle:  (jdk7-b125 PIT)
http://rehudson.sfbay.sun.com/hudsonws/deploypit/bundles
[Build - b255-2011-01-06_23 

* Tested OS: x86 Windows

* Issue:
Setting the java deployment cache size to 100M and after launching several different applications, the size of the cache directory is over 200M
Comments
Closed as Won't Fix. Please re-open this bug if you regard this as an important issue.
18-03-2014
EVALUATION I just ran a set of tests on Windows XP + JDK 7u3 machine and confirmed that the fix for CR 6932885 works as expected. The test plan was as described in CR 6932885. I limited the deployment cache size to 50 MB and watched its size after every JNLP application launch. It was the following sequence of numbers: ... 48058191 48186671 49425306 84773150 53010095 48612904 52749497 The entry 84773150 appeared after installation of a quite big application. So, the fix for CR 6932885 works just as expected. It is known that its behavior is not ideal. For example, the actual cache size is usually slightly higher that the configured limit, and in some cases it may be significantly higher (like in the case above). This is a subject for further cleanup logic enhancements.
21-03-2012