You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"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.
Activity
davewhat commentedon Feb 4, 2016
I'm having issues running TChannel-Java with Hyperbahn on Vagrant boxes.
When I tcap, I see the following:
In the Hyperbahn log file I am seeing:
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
tchannel-java/tchannel-core/src/main/java/com/uber/tchannel/api/TChannel.java
Line 135 in a38de37
nath-uber commentedon Feb 24, 2016
Tested on my dev box and it should work
4262eac