apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjay M Pujare (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-760) Webapp tracking URL does not include full qualified hostname
Date Fri, 14 Jul 2017 01:32:00 GMT

    [ https://issues.apache.org/jira/browse/APEXCORE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086704#comment-16086704
] 

Sanjay M Pujare commented on APEXCORE-760:
------------------------------------------

Could this be a host configuration issue on the app master and not a bug in the app master
Web service? If that host is configured with the full qualified hostname for the listen address
may be this will work?

The StreamingApoMasterService uses org.apache.hadoop.net.NetUtils.getConnectAddress(InetSocketAddress)
to create the appMaster tracking URL and this method does claim to "Return an InetSocketAddress
that a client can use to connect to the given listening address.". And it calls getHostName()
on that InetSocketAddress

> Webapp tracking URL does not include full qualified hostname
> ------------------------------------------------------------
>
>                 Key: APEXCORE-760
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-760
>             Project: Apache Apex Core
>          Issue Type: Bug
>    Affects Versions: 3.6.0
>            Reporter: Thomas Weise
>            Assignee: Thomas Weise
>
> The app master tracking URL that gets registered with the RM does not contain the full
name, leading to mismatch in SSL certificate check.
> Instead of https://host:34112 it should be https://host.domain.com:34112



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message