JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-276  -  The management port of a server-local node cannot be configured separately
Posted May 25, 2014 - updated Jun 01, 2014
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Bug report
  • Status
     
    Closed
  • Assigned to
     lolo4j
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     lolo4j
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    Node
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Reproducability
    Always
  • Severity
    Low
  • Targetted for
    icon_milestones.png JPPF 4.1.2
Issue description
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.
Steps to reproduce this issue
This is missing code, no reproduction step needed

#3
Comment posted by
 lolo4j
Jun 01, 13:37
Fixed in: