JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-473  -  Incorrect classpath configured in wrapper-driver.conf and wrapper-node.conf
Posted Sep 01, 2016 - updated Sep 09, 2016
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
    Configuration
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Reproducability
    Always
  • Severity
    Low
  • Targetted for
    icon_milestones.png JPPF 5.2.2
Issue description
In the driver and node distrbutions, the Java service wrapper configuration has incorrect values for the jppf-jmsremote_optional jar.

In wrapper-driver.conf the following:
wrapper.java.classpath.8=lib/jppf-jmxremote_optional-1.1.1.jar
should be replaced with
wrapper.java.classpath.8=lib/jppf-jmxremote_optional-1.2.jar
In wrapper-node.conf the following:
wrapper.java.classpath.7=lib/jppf-jmxremote_optional-1.1.1.jar
should be replaced with
wrapper.java.classpath.7=lib/jppf-jmxremote_optional-1.2.jar
Furhtermore, as of v5.2 the jppf-*.jar definitions are missing the version number in the jar names. In wrapper-driver.conf of v5.2.1:
wrapper.java.classpath.2=lib/jppf-common.jar
wrapper.java.classpath.3=lib/jppf-server.jar
wrapper.java.classpath.4=lib/jppf-node.jar
should be replaced with:
wrapper.java.classpath.2=lib/jppf-common-5.2.1.jar
wrapper.java.classpath.3=lib/jppf-server-5.2.1.jar
wrapper.java.classpath.4=lib/jppf-node-5.2.1.jar
In wrapper-node.conf:
wrapper.java.classpath.2=lib/jppf-common.jar
wrapper.java.classpath.3=lib/jppf-node.jar
should be replaced with:
wrapper.java.classpath.2=lib/jppf-common-5.2.1.jar
wrapper.java.classpath.3=lib/jppf-node-5.2.1.jar
Steps to reproduce this issue
Conifgure a driver and node to run as a services or daemons and launch them

#6
Comment posted by
 lolo4j
Sep 09, 06:15
Fixed in: