JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Bug report JPPF-88  -  Nodes and drivers running as services cannot be restarted via JMX
Posted Oct 26, 2012 - updated Oct 26, 2012
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.2
Issue description
When running a node or driver as servie/daemon, using the Java Service Wrapper, attempts to restart them will fail: the node or driver will simply stop, but not be restarted.

This is de to the fact that, as a standalone application, a node or driver is actually launched as a subprocess, where the main process watches for a Java exit code = 2, in which case it rerstarts the subprocess.

To have an equivalent behavior with the Java service wrapper, one has to add the following properties to the Java service wrapper configuration file (wrapper-node.conf or wrapper-driver.conf):
Steps to reproduce this issue
start a node or driver as a service or daemon and try to restart it via the admin console: the node stops but does not restart

Comment posted by
Oct 26, 07:53
Fixes 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.