[ 
https://issues.apache.org/jira/browse/TC-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryan Durfey updated TC-157:
---------------------------
    Attachment: text.html

Zhilin,

Thanks for the feedback on these. I am working on getting additional committers 
involved.

Ryan Durfey    M | 303-524-5099
CDN Support (24x7): 866-405-2993 or 
[email protected]<mailto:[email protected]>


From: "Zhilin Huang (JIRA)" <[email protected]>
Date: Thursday, June 15, 2017 at 1:18 AM
To: Ryan Durfey <[email protected]>
Subject: [jira] [Commented] (TC-157) Failed to restart tomcat in Traffic Router 
when failed to get SSL keys


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

Zhilin Huang commented on TC-157:
---------------------------------

I don't think so, the PR is still open.

Failed to restart tomcat in Traffic Router when failed to get SSL keys
----------------------------------------------------------------------

                 Key: TC-157
                 URL: https://issues.apache.org/jira/browse/TC-157
             Project: Traffic Control
          Issue Type: Bug
          Components: Traffic Router
    Affects Versions: 1.7.0
            Reporter: Zhilin Huang
            Assignee: Zhilin Huang
              Labels: ssl, tomcat

Stopping tomcat failed with the following log:
WARN  2017-02-17T09:00:05.939 [main] 
com.comcast.cdn.traffic_control.traffic_router.core.secure.CertificatesPublisher
 - Detected destroy setting running to false
INFO  2017-02-17T09:00:05.943 [pool-2-thread-1] 
com.comcast.cdn.traffic_control.traffic_router.core.secure.CertificatesClient - 
Interrupted while pausing for check of traffic ops config
INFO  2017-02-17T09:00:05.943 [pool-2-thread-1] 
com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - POSTing: 
https://192.168.122.181/api/1.1/user/login; timeout is 15000
INFO  2017-02-17T09:00:06.005 [pool-2-thread-1] 
com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - GETing: 
https://192.168.122.181/api/1.2/cdns/name/kabletown_cdn/sslkeys.jso
n; timeout is 15000
WARN  2017-02-17T09:00:06.040 [pool-2-thread-1] 
com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - Failed Http 
Request to https://192.168.122.181/api/1.2/cdns/name/kabletown_
cdn/sslkeys.json Status 400



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




> Failed to restart tomcat in Traffic Router when failed to get SSL keys
> ----------------------------------------------------------------------
>
>                 Key: TC-157
>                 URL: https://issues.apache.org/jira/browse/TC-157
>             Project: Traffic Control
>          Issue Type: Bug
>          Components: Traffic Router
>    Affects Versions: 1.7.0
>            Reporter: Zhilin Huang
>            Assignee: Zhilin Huang
>              Labels: ssl, tomcat
>         Attachments: text.html
>
>
> Stopping tomcat failed with the following log:
> WARN  2017-02-17T09:00:05.939 [main] 
> com.comcast.cdn.traffic_control.traffic_router.core.secure.CertificatesPublisher
>  - Detected destroy setting running to false
> INFO  2017-02-17T09:00:05.943 [pool-2-thread-1] 
> com.comcast.cdn.traffic_control.traffic_router.core.secure.CertificatesClient 
> - Interrupted while pausing for check of traffic ops config
> INFO  2017-02-17T09:00:05.943 [pool-2-thread-1] 
> com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - POSTing: 
> https://192.168.122.181/api/1.1/user/login; timeout is 15000
> INFO  2017-02-17T09:00:06.005 [pool-2-thread-1] 
> com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - GETing: 
> https://192.168.122.181/api/1.2/cdns/name/kabletown_cdn/sslkeys.jso
> n; timeout is 15000
> WARN  2017-02-17T09:00:06.040 [pool-2-thread-1] 
> com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - Failed 
> Http Request to https://192.168.122.181/api/1.2/cdns/name/kabletown_
> cdn/sslkeys.json Status 400



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

Reply via email to