JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-571  -  Driver started with JPPFDriver noLauncher exits immediately when jppf.discovery.enabled=false
Posted Jan 05, 2019 - updated Jan 05, 2019
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
    Server
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Reproducability
    Always
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 6.0.2
Issue description
When starting a driver using the main class org.jppf.server.JPPFDriver, with the argument "noLauncher", the driver will exit immediately after its initialization, when UDP multicast discovery is disabled, that is, when the configuration property "jppf.discovery.enabled" is set to "false"

This is due to the fact that the UDP broadcast thread is the only non-dameon thread started at driver startup. The driver startup essentially starts new threads, and nothing prevents it from exiting the JVM when only daemon threads are started.
Steps to reproduce this issue
see description

#3
Comment posted by
lolo4j
Jan 05, 18:28
Fixed, delivered patch 01 for JPPF 6.0.1

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from New to Closed.
  • 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.