JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Enhancement JPPF-149  -  Enable on-demand cleanup of class loader resource cache
Posted May 21, 2013 - updated Dec 27, 2014
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
  • Status
  • Assigned to
  • Progress
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
  • Owned by
    Not owned by anyone
  • Category
  • Resolution
  • Priority
  • Targetted for
    icon_milestones.png JPPF 3.3.x
Issue description
Sometimes, the resource cache of a client class loader can hold a large number of files, which can cause it to fill the temp files folder. This may happen even if the class loader cache size is set to 1. For instance, in a situation where a single client submits a lot of jobs whose tasks invoke ClassLoader.getResourceXXX() methods.

We propose to implement the ability to request resource cache cleanups on demand, via direct API calls or management requests. A cleanup request may not result in an immediate cleanup, but rather in a differed cleanup at a time when this will not interfere with the execution of a job. The best time to do so would be when the job header is loaded into the node, or just before the tasks are loaded.

Comment posted by
May 24, 00:07
This is now implemented. Changes committed to SVN:

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from Confirmed to Closed.
  • This issue's progression has been updated to 100 percent completed.
  • The resolution has been updated, from Not determined to RESOLVED.
  • Information about the user working on this issue has been changed, from lolo4j to Not being worked on.