JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Bug report JPPF-174  -  Thread context class loader is null for client-local execution
Posted Jul 27, 2013 - updated Dec 27, 2014
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Bug report
  • 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
  • Reproducability
  • Severity
  • Targetted for
    icon_milestones.png JPPF 3.3.x
Issue description
When a task is executing locally in the client, its thread context class loader is always null. This can lead to exceptions or errors, especially when the task generates dynamic classes (for instance with javassist, bcel, etc...)
Steps to reproduce this issue
run the following task locally:
public MyTask extends JPPFTask {
  public void run() {
    System.out.println("thread context class loader = " + Thread.currentThread().getContextClassLoader();
==> the node output console will show that the class loader is null

Comment posted by
Jul 28, 08:35
Fixed. Changes committed to SVN:

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.