JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-542  -  Job dispatch expiration does not work in multi-server topology
Posted Jul 24, 2018 - updated Jul 25, 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
    Server
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Reproducability
    Always
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 5.2.10
Issue description
When setting job dispatch expiration in a multi-server toplogy where the serers communicate with each other, if a job is dispatched by driver D1 to its peer driver D2, then upon expiration the job is not cancelled is D2 and remains stuck there unless manually cancelled (via the admin console or via API).
Steps to reproduce this issue
Using a topology with 2 drviers D1 and D2, 1 node N1 attached to D1 (D2 has no node) and the attached configurations, submit 2 jobs using the attached client code: we can observe that a job remains stuck in D2. See also attached screenshots.

#2
Comment posted by
 lolo4j
Jul 24, 08:54
A file was uploaded. reproducing.zipicon_open_new.png
#3
Comment posted by
 lolo4j
Jul 24, 08:54
A file was uploaded.
Topology.png
Topology.pngicon_open_new.png
#4
Comment posted by
 lolo4j
Jul 24, 08:55
A file was uploaded.
Jobs.png
Jobs.pngicon_open_new.png