JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
enhancement_small.png
CLOSED  Enhancement JPPF-362  -  Ability for the cient to handle multiple class loaders per job
Posted Feb 01, 2015 - updated Feb 04, 2015
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.2.6
Issue description
Currently, when looking up a resource in response to a class loading request coming from a node, the JPPF client only uses a single class loader that was associated with the corresponding job right after it was submitted. This can cause problems if some of the tasks in the job were loaded with different class loaders, or in edge cases such as when a job is submitted from a task executing in a node, and a task in this job requires one or more classes that are not in the node's classpath, but are in the initial client's classpath.

This enhancement is about adding the ability, via a specific API, to add/get/remove other class loaders for the job. There should be an API available in JPPFClient or its super classes, and another in the JobConfiugration to use with a JPPFExecutorService.

#4
Comment posted by
 lolo4j
Feb 04, 11:48
Implemented in: