JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
enhancement_small.png
CLOSED  Enhancement JPPF-389  -  Improvements for node host name resolution
Posted Apr 28, 2015 - updated Apr 29, 2015
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Enhancement
  • Status
     
    Closed
  • Assigned to
     lolo4j
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Server
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 5.0.2
Issue description
Currently, the resolution of host names in the driver, which is the one used by the admin console, is essentially performed via a reverse DNS lookup. In some situation, such as private addresses in a cloud setup, thuis lookup will fail, and only the ip address will be displayed in the conosle.

We propose to resolve the host name nonetheless, based on the JPPFSystemInformation.getNetwork() data provided by the node upon handshaking with the server. Indeed, the node may have a locally available host name which cannot be resolved on the driver machine.

#3
Comment posted by
 lolo4j
Apr 29, 08:11
Fixed in: