JPPF Issue Tracker
Please log in to bookmark issues
OPEN  Feature request JPPF-436  -  Integration of JMX remote with NIO
Posted Feb 01, 2016 - updated Oct 09, 2017
lolo4j (lolocohen) has been working on this issue since October 09, 2017 (07:28)
Issue details
  • Type of issue
    Feature request
  • Status
  • Assigned to
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
  • Owned by
    Not owned by anyone
  • Category
    JMX connector
  • Resolution
    Not determined
  • Priority
  • Targetted for
    icon_milestones.png JPPF 6.0
Issue description
The goal is to make the JMX generic/JMXMP connector available via NIO (socket channels) rather than straight Sockets on the server side.

One of the main benefits is that it will allow us to use a shared thread poool for all JMX client connections. This should result in a much reduced number of threads running in the driver, due to its JMX connections to all the nodes: instead of 2 threads per node, there would be at most the number of threads in the pool.

Along with scalability and performance improvements, this will allow us to get rid of the separate management port used in the JPPF configuration, since it will use the same port as the other services (e.g. the default 11111 port).