[jira] [Commented] (TC-173) API on port 3333 doesn't start if 443 is first in server.xml

["Hank Beatty (JIRA)" <ji...@apache.org>]

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

Hank Beatty commented on TC-173:
--------------------------------

It appears the port start order has become random. As you can see below 3333, 443, then 80. This negates the fix we had previously of putting 3333 before 443. This order kept 80 from starting.

May 04, 2017 10:13:59 AM com.comcast.cdn.traffic_control.traffic_router.protocol.LanguidPoller run INFO: Traffic Router published the ready state; calling init() on our reference to Connector with a listen port of 3333 May 04, 2017 10:13:59 AM com.comcast.cdn.traffic_control.traffic_router.protocol.LanguidPoller run INFO: Traffic Router published the ready state; calling init() on our reference to Connector with a listen port of 443 May 04, 2017 10:13:59 AM com.comcast.cdn.traffic_control.traffic_router.protocol.LanguidPoller run INFO: Traffic Router published the ready state; calling init() on our reference to Connector with a listen port of 80

> API on port 3333 doesn't start if 443 is first in server.xml
> ------------------------------------------------------------
>
>                 Key: TC-173
>                 URL: https://issues.apache.org/jira/browse/TC-173
>             Project: Traffic Control
>          Issue Type: Bug
>          Components: Traffic Router
>    Affects Versions: 1.8.0, 1.7.0
>         Environment: CentOS 6
>            Reporter: Hank Beatty
>            Priority: Minor
>
> I didn't have any certs installed on the Traffic Router so the https portion couldn't start.
> It was suggested that TR should check to see if there are certs before trying to start 443 connector.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)