JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
enhancement_small.png
CLOSED  Enhancement JPPF-468  -  Add connection/executor information to job events on the client side
Posted Aug 16, 2016 - updated Feb 23, 2017
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Not a bug" and resolution "NOT AN ISSUE".
Issue details
  • Type of issue
    Enhancement
  • Status
     
    Not a bug
  • Assigned to
    Not assigned to anyone
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Client
  • Resolution
    NOT AN ISSUE
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 6.0
Issue description
We propose to add, for JobListener.jobDispatched() and JobListener.jobReturned() notifications, a reference to the JPPFClientConnection through which the job was dispatched. In the case of a client local executor, the reference would be null, thus we could also add a flag such as isLocalExecution() to make the distinction clear and easy.

Basically we would add the following to JobEvent:
public class JobEvent extends EventObject {
  // Get the connection through which the job was dispatched or returned
  public JPPFClientConnection getConnection()
 
  // Whether the job was dispatched to or returned from the local executor
  public boolean isLocalExecution()
}

#2
Comment posted by
 lolo4j
Feb 23, 17:13
This functionality already exists side 4.2. Closing ths enhancement.