JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Bug report JPPF-145  -  Node execution manager does not clean up the data provider after job execution
Posted May 11, 2013 - updated Dec 27, 2014
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Bug report
  • Status
  • Assigned to
  • Progress
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
  • Owned by
  • Category
  • Resolution
  • Priority
  • Reproducability
  • Severity
  • Targetted for
    icon_milestones.png JPPF 3.3.x
Issue description
After executing the tasks of a job, NodeExecutionManagerImpl does not clean up its dataProvider attribute, which then occupies memory for no reason, at least until the next job arrives.
Steps to reproduce this issue
  • Run the matrix multiplication sample, with a sufficiently large matrix (1000*1000 is ok) and a single node
  • Perform a GC on the node from the admin console
  • Take a heap dump of the node using the admin console
  • ==> the heap dump analysis with Eclipse MAT shows that almost all the memory is taken by a Matrix object, which is in fact sent to the node with the DataProvider

Comment posted by
May 11, 12:14
Fixed. 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.