JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-483  -  ConcurrentModificationException in AbstractExecutionManager
Posted Dec 30, 2016 - updated Dec 30, 2016
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Bug report
  • Status
     
    		 Closed
  • Assigned to
    lolo4j
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Node
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Reproducability
    Often
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 5.2.4
Issue description
While investigating an automated test failure, I found out that sometimes cancelling a job can cause a node to fail if the node is just starting to execute the job.

This is due to a lack of synchronization in AbstractExecutionManager which leads to an intermittent ConcurrentModificationException.
Steps to reproduce this issue
Try and submit jobs, then cancel them shortly thereafter. If you do it a sufficient number of times, you eventually manage to reproduce

#3
Comment posted by
lolo4j
Dec 30, 07:57
Fixed in: