JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-370  -  Topology manager timer threads do not terminate
Posted Feb 15, 2015 - updated Feb 15, 2015
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
    Not assigned to anyone
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Client
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Reproducability
    Always
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 5.0
Issue description
The TopologyManager uses two timers for the NodeRefreshHandler and the JVMHealthRefreshHandler, whose threads are not currently defined as daemons. This causes an application using the montoring API to not terminate because these 2 threads are not active. We should either add a close() method to TopologyManager (and make it implement AutoCloseable) or make the threads as daemons, or both.
Steps to reproduce this issue
  • create a TopologyManager instance
  • let the applicatiton terminate normally (no System.exit(x))
==> the application does not in fact terminate. Upon taking a thread dump, 3 related threds are still active: "JPPF Topology Update Timer", "JVM Health Update Timer" and "TopologyEvents_0001". The last one should not need any special action, as it is already defined as a daemon thread.

#2
Comment posted by
lolo4j
Feb 15, 13:20
fixed in trunk revision 3569