JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-402  -  Bad synchronization in provisioning code prevents tiemly fulfillment of provisioning requests
Posted Jul 03, 2015 - updated Aug 15, 2018
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
    Not determined
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 5.0.x
Issue description
Due to the way the methods are synchronized in class org.jppf.node.provisioning.SlaveNodeManager, the notification that a slave node was effectively stopped can only happen after exiting the provisioning method. This causes the master node to not know the state of the slave and prevents it from performing the associated updates/cleanup
Steps to reproduce this issue
N/A

#3
Comment posted by
lolo4j
Jul 04, 20:05
Fixed in: