JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Bug report JPPF-276  -  The management port of a server-local node cannot be configured separately
Posted May 25, 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.1.x
Issue description
The server and node configurations use the same property "" to define the port of their respective JMX remote connector. In the case of the server, this property is used for plain (unsecure) connections, as there is a separate "" for SSL connections. In any case, there is an overlap and it is not possible to define the node's management port separately.

Note that in this scenario, JPPF will automatically assign the first available port after the one specified (or after the default 11198), as the JMX connector server startup code checks for already bound ports.

What we propose is to use a newx property for the node, e.g. "", deprecate "" for the nodes, and still look for it when the new property is not defined, for backward compatibility.
Steps to reproduce this issue
This is missing code, no reproduction step needed

Comment posted by
Jun 01, 13:37
Fixed in: