JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
enhancement_small.png
CLOSED  Enhancement JPPF-257  -  Better exception handling for overriden or custom TaskResultListener implementations
Posted May 05, 2014 - updated May 10, 2014
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Enhancement
  • Status
     
    Closed
  • Assigned to
     lolo4j
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Client
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 4.1.1
Issue description
When a user overrides the resultsReceived() method of a TaskResultListener implementation, such as JPPFResultCollector, we do not handle any exception that might be thrown by the user code. The problem wiht that is that is causes the connection currently executing the job to disconnect and attempt to reconnect.

This behavior doesn't make much sense, since this happens when the connection is actually not involved: as its name indicates, resultsReceived() is called after results were received from the server and any eventual I/O errors have already been handled. I rpopose that we catch exceptions raised by resultsReceived() and at least log them with full stack trace at ERROR/SEVERE level to attract the user's attention to it. Maybe add a syserr message referring to the log?

#4
Comment posted by
 lolo4j
May 10, 18:56
Implemented in: