JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Enhancement JPPF-190  -  Improve handling of deserialization errors in the nodes
Posted Sep 30, 2013 - updated Oct 03, 2013
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
  • 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 4.0
Issue description
Currently, when an error occurs while deserializng a task from a dispatched bundle, all tasks are marked with the first error encoutered and returned unexecuted to the server. Unfortunately, after looking in the code, this error is not sent back to the client, so these tasks are just returned unexecuted, with no additional information.

We propose the following enhancements:
  • the tasks that can be deserialized should be executed by the node
  • for the the tasks that can be deserialized, substitute an object holding the throwable that was raised, for instance a JPPFExceptionResult or something equivalent. When these 'fake' task results are received on the client, the client should retrieve the original task and set this throwable upon it, then use it as result.
  • the same enahancement should also apply to tasks whose serialization fail after their execution

Comment posted by
Oct 03, 07:24
Implemented. Changes committed to SVN trunk revision 2898

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