JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-91  -  NPE: in class loaders when AbstractJPPFClassLoaderLifeCycle:loadRemoteData return NULL
Posted Oct 26, 2012 - updated Nov 09, 2012
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
    jandam
  • Owned by
    Not owned by anyone
  • Category
    Client
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Reproducability
    Rarely
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 3.2
Issue description
Result of ResourceFuture can be set to NULL. This leads to NPEs in JPPF class loaders. The Future should be cancelled instead of value set to null.
Steps to reproduce this issue
Reproducible only during problems with connections or errors during class loading.

#3
Comment posted by
jandam
Oct 26, 16:38
In some scenarios computeValue returns original Callable instead of NULL result
#5
Comment posted by
jandam
Oct 28, 23:37
There are several problems in class loading. Issues are in previous versions.
  • computeValue: when node disconnects from driver Exception is correctly thrown. When driver disconnects from client - no exception is thrown and original Callable is returned that can lead to ClassCastException in user code.
  • 3.2 only: class loading can lead to NPE
  • 3.2 only: Resource can be incorrectly added to 'not found cache' when error occurs during transfer.
All above mentioned scenarios need to be properly tested and fixed.
#7
Comment posted by
lolo4j
Nov 09, 09:43
Fixed in trunk revision 2539

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.