JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Bug report JPPF-320  -  Node reports unreachable JMX host in some configurations
Posted Sep 04, 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
    Not determined
  • Severity
  • Targetted for
    icon_milestones.png JPPF 4.2.x
Issue description
From this forum thread. The scenario is as follows:
  • node and driver are on two separate machines and not on the same local network
  • the node connects to the driver via VPN (so they are on the same VPN network)
  • the connection works except for JMX, due to the node's JMX server reporting its local network address instead of the VPN address
This is due to the node host address being computed solely via NetworkUtils.getNonLocalHostAddress() which simply takes the first IP address of the first network interface with a non-local IP that it explores.
Steps to reproduce this issue
N/A. I need to install a VPN server to reproduce, I will update then.

Comment posted by
Sep 09, 19:14
It turned out to be a firewall configuration issue, where the server port (11111) was not opened on the node side.