The server and node configurations use the same property "jppf.management.port" 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 "jppf.management.ssl.port" 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. "jppf.node.management.port", deprecate "jppf.management.port" for the nodes, and still look for it when the new property is not defined, for backward compatibility.