JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-78  -  Generic serializer throws a ClassFormatError
Posted Oct 12, 2012 - updated Oct 12, 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
    lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Customization
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Reproducability
    Often
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 3.2
Issue description
When starting a driver and a node, both configured with "jppf.object.stream.builder = org.jppf.serialization.GenericObjectStreamBuilder", I get the following stack trace in the node's console output: 

Exception in thread "main" java.lang.ClassFormatError: Incompatible magic value 0 in class file org/jppf/server/node/remote/JPPFRemoteNode
  at java.lang.ClassLoader.defineClass1(Native Method)
  at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
  at java.lang.ClassLoader.defineClass(ClassLoader.java:634)
  at org.jppf.classloader.AbstractJPPFClassLoader.findClass(AbstractJPPFClassLoader.java:153)
  at org.jppf.classloader.AbstractJPPFClassLoader.loadJPPFClass(AbstractJPPFClassLoader.java:97)
  at org.jppf.node.NodeRunner.createNode(NodeRunner.java:194)
  at org.jppf.node.NodeRunner.main(NodeRunner.java:141)
Steps to reproduce this issue
  • add "jppf.object.stream.builder = org.jppf.serialization.GenericObjectStreamBuilder" to the driver's configuration
  • add "jppf.object.stream.builder = org.jppf.serialization.GenericObjectStreamBuilder" to the node's configuration
  • start the driver
  • start the node
  • ==> you get the error



#3
Comment posted by
lolo4j
Oct 12, 20:17
Fixed. Chnages 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.