JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Feature request JPPF-35  -  Job submission through multiple channels
Posted Aug 08, 2012 - updated Oct 18, 2012
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Feature request
  • Status
  • Assigned to
  • Progress
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
  • Owned by
    Not owned by anyone
  • Category
  • Resolution
  • Priority
  • Targetted for
    icon_milestones.png JPPF 3.2
Issue description
Steps to reproduce: 1 Job with 2 tasks. Client + 1 driver (pool.size = 2) + 1 node. Each task (same jobUUID) is send to driver through different connection. Driver sends for execution only one task or task result is returned through different channel. This scenario is reproducible only with new load balancer. Old load balancer uses only one channel for sending all tasks. Tested workarounds:

1) generate new jobUUID for each submitted task -> job cancellation through driver MBean stops working - non existent jobUUID

2) add connection.uuid. to UuidPath (= format: <clientUUID, connection.uuid> - driver notifies 2x jobQueued, jobEnded. No tasks executed on node. This is blocker for new load balancer.

Originally it was not intended for splitting job into multiple connections. This need to be investigated after async communication with nodes will be implemented.

Comment posted by
Oct 18, 11:23
Fixed by commit in trunk revision 2482

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from Being worked on 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 jandam to Not being worked on.