JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Bug report JPPF-249  -  JMXMP creating "JMX server connection timeout Thread-*" threads for each client connection
Posted Apr 19, 2014 - updated Mar 28, 2016
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 4.0.x
Issue description
The JMXMP connector is creating at least one "JMX server connection timeout Thread-*" thread in server for each client connection. From the specs of the generic connector, these threads, which check and close a connection after it's been idle for more than a specified timeout, can be avoided if we specify a timeout value equal to Long.MAX_VALUE:
Map<String, Object> env = new HashMap<>();
env.put("jmx.remote.x.server.connection.timeout", Long.MAX_VALUE);
Steps to reproduce this issue
  • start a driver and a client with 50 connection
  • inspect the driver with a tool such as VisualVM or JConsole and lok at the threads:
  • ==> there will be 50 threads named "JMX server connection timeout Thread-1" ... "JMX server connection timeout Thread-50"

Comment posted by
Apr 19, 06:32
Added configurable timer intervals for servers stats, topology, jvm health and job data views in