JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-185  -  NoClassDefFoundError in JPPFNode.reset()
Posted Sep 06, 2013 - updated Sep 13, 2013
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
     lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Node
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Reproducability
    Rarely
  • Severity
    Not determined
  • Targetted for
    icon_milestones.png JPPF 3.3.6
Issue description
A user reported the following stack trace in the nodes, at the time the server was terminated:
Exception in thread "main" java.lang.NoClassDefFoundError: org/jppf/management/spi/JPPFMBeanProviderManager
  at org.jppf.server.node.JPPFNode.reset(JPPFNode.java:409)
  at org.jppf.server.node.JPPFNode.run(JPPFNode.java:128)
  at org.jppf.node.NodeRunner.main(NodeRunner.java:142)
Caused by: java.lang.ClassNotFoundException: could not find resource org.jppf.management.spi.JPPFMBeanProviderManager
  at org.jppf.classloader.AbstractJPPFClassLoader.findClass(AbstractJPPFClassLoader.java:145)
  at org.jppf.classloader.AbstractJPPFClassLoader.findClass(AbstractJPPFClassLoader.java:113)
  at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
  at org.jppf.classloader.AbstractJPPFClassLoader.loadClass(AbstractJPPFClassLoader.java:432)
  at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
  ... 3 more
Steps to reproduce this issue
I cannot reproduce but several forum users can.

#3
Comment posted by
 lolo4j
Sep 13, 20:25
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 New 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.