JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Bug report JPPF-122  -  JMX connection threads leak in the driver
Posted Feb 06, 2013 - 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
Issue description
When a node is disconnected from the driver, the JMXConnectionThread instance held by the corresponding JMXNodeConnectionWrapper keeps running in WAIT state.

It would appear that we do not close the JMX connection properly and/or that we do not terminate the thread.

This can result over time in many threads still alive in the JVM with a call stack similar to this:
"JMX connection" daemon prio=6 tid=0x000000000b4d3000 nid=0x104c in Object.wait() [0x000000001cdaf000]
java.lang.Thread.State: WAITING (on object monitor)
  at java.lang.Object.wait(Native Method)
  at java.lang.Object.wait(
  at org.jppf.utils.ThreadSynchronization.goToSleep(
  - locked <0x00000000f5972d30> (a
Locked ownable synchronizers:
  - None
Steps to reproduce this issue
  • start 1 driver
  • start as many nodes as possible (tyhe more the better for reproducing)
  • start the admin console
  • in the console select all nodes then click on the "Restart node" button
  • do the previous a number of times
  • take a thread dump of the driver's JVM ==> you will see many threads as described above

Comment posted by
Feb 06, 08:40
A file was uploaded. A driver thread dump illustrating the issueicon_open_new.png
Comment posted by
Feb 06, 15:03
Fixed. Changes committed to SVN:

The issue was updated with the following change(s):
  • The assignee has been changed to lolo4j.
  • This issue has been closed
  • The status has been updated, from New to Closed.
  • This issue's progression has been updated to 100 percent completed.
  • The resolution has been updated, from Not determined to RESOLVED.