JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Bug report JPPF-304  -  Node default connection strategy uses incorrect default server port with manual settings
Posted Aug 08, 2014 - updated Aug 15, 2018
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.2.x
Issue description
When, in the node configuration, discovery is enabled, no default port is specified and no connection strategy is specified, the node uses by default 11143 for the server port when SSL is disabled, and 11111 if SSL is enabled. It shoulld be the opposite: 11111 with SSL disabled and 11143 with SSL enabled.

I could track the issue in the code of org.jppf.node.connection.JPPFDefaultConnectionStrategy, in method connectionFromManualConfiguration() there is this line:
int port = config.getInt("jppf.server.port", ssl ? 11111 : 11143);
this is incorrect, the fix is to modify it as follows:
int port = config.getInt("jppf.server.port", ssl ? 11143 : 11111);
Steps to reproduce this issue
  • start a driver
  • in the node configuration, set:
    • jppf.discovery.enabled = false
    • comment out the server port: #jppf.server.port = 11111
    • comment out the SSL switch: #jppf.ssl.enabled = true
  • start the node
  • ==> you can see the node trying to connect to the server on port 11143

Comment posted by
Aug 08, 06:55
fixed in: