Skip to content

IP Hostname is not correct in some hosts. #121

Open

Description

@jc-fireball
No description provided.

Activity

  1. davewhat commented on Feb 4, 2016

    @davewhat

    I'm having issues running TChannel-Java with Hyperbahn on Vagrant boxes.

    When I tcap, I see the following:

    session=129 127.0.0.1:42779 --> 127.0.0.1:21300 frame=0 type=0x01
    INIT REQUEST id=0x0000 (0) version=2
    headers
      host_port: ip-10-12-55-225.us-west-2.compute.internal:49795
      process_name: java-process
    
    session=129 ended src=127.0.0.1:42779 --> dst=127.0.0.1:21300 on lo
    

    In the Hyperbahn log file I am seeing:

    "error": {
      "type": "tchannel.invalid-init-host-port",
      "message": "invalid host:port string in init header",
      "hostPort": "ip-10-12-55-225.us-west-2.compute.internal:61708",
      "name": "TchannelInvalidInitHostPortError",
      "reason": "Expected host to contain IPv4 in \"ip-10-12-55-225.us-west-2.compute.internal:61708\"",
      "fullType": "tchannel.invalid-init-host-port"
    

    I think the problem is that we have a string host name, and not just an IP address of xxx.xxx.xxx.xxx
    Seems like TChannel.java is getting a DNS style host name.

    I think the issue is

    this.listeningHost = localAddress.getHostName();

  2. nath-uber commented on Feb 24, 2016

    @nath-uber
    Contributor

    Tested on my dev box and it should work
    4262eac

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions