JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Bug report JPPF-248  -  Node fails to restart via JMX
Posted Apr 16, 2014 - 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 node restart is requested via the administration console or directly via the management API, it disconnects from the server but fails to reconnect properly. The node's log shows that it is stuck in an infinite loop trying to reconnect, with the following lines repeating ad eternam:
2014-04-15 20:33:47,757 [INFO ][]: maxBatchSize = 1
2014-04-15 20:33:47,803 [INFO ][org.jppf.server.node.NodeExecutionManagerImpl.<init>(132)]: running 8 processing threads
2014-04-15 20:33:47,803 [INFO ][org.jppf.server.node.NodeExecutionManagerImpl.createThreadManager(159)]: Using default thread manager
This only happens in v3.3.7, not in 4.0.2 nor in the trunk.
Steps to reproduce this issue
  • start a server, a node and the administration console
  • in the console, select the node and click on the "node restart" button
  • ==> the node disappears but does not reappear again, and its log shows the statements mentioned in the bug description

Comment posted by
Apr 16, 04:57
Fixed in branch b3.3 revision 3130