JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Bug report JPPF-97  -  OutOfMemoryError in the driver when using multiple client connections
Posted Nov 10, 2012 - 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
    Not assigned to anyone
  • Progress
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
  • Owned by
    Not owned by anyone
  • Category
  • Resolution
  • Priority
  • Reproducability
  • Severity
  • Targetted for
    icon_milestones.png JPPF 3.1.x
Issue description
In some conditions, when the driver uses multiple connections to the driver (connection pool), the driver crashes with an OOME. From the attached heapdump, it appears that entries are not released properly in org.jppf.server.queue.JPPFPriorityQueue.sizeMap

I need to check if this happens in the trunk too.
Steps to reproduce this issue
Using the attached code sample and driver and client config files:
  • start one driver and 2 nodes
  • run the client runner application (OOMEJobRunner class)
  • ==> after some time, you get an OOME in the driver

Comment posted by
Nov 10, 09:46
A file was uploaded. Generated heap dumpicon_open_new.png
Comment posted by
Nov 10, 09:47
A file was uploaded. reproducing sample code and configurationicon_open_new.png
Comment posted by
Nov 12, 09:08
Fixed in branch b3.1 revision 2542

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from New to Closed.
  • This issue's progression has been updated to 100 percent completed.
  • The resolution has been updated, from Not determined to RESOLVED.