[
https://issues.apache.org/jira/browse/TC-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833253#comment-15833253
]
ASF GitHub Bot commented on TC-114:
-----------------------------------
GitHub user zhilhuan opened a pull request:
https://github.com/apache/incubator-trafficcontrol/pull/210
[TC-114] always make sure the run loop exit when shutting down
Make sure to execute "isActive" check in the loop. Otherwise, if no
CrConfig, the check will be skipped. And Tomcat could not be stopped gracefully.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zhilhuan/incubator-trafficcontrol TC-114
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-trafficcontrol/pull/210.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #210
----
commit 4f2db132d80903ca86a4a5216cbd037ee0f24475
Author: Zhilin Huang <zhilh...@cisco.com>
Date: 2017-01-22T02:58:33Z
always make sure the run loop exit when shutting down
----
> Fail to restart Tomcat when TM start before config pulled
> ---------------------------------------------------------
>
> Key: TC-114
> URL: https://issues.apache.org/jira/browse/TC-114
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Monitor
> Affects Versions: 1.7.0
> Reporter: Zhilin Huang
>
> Here are the steps to reproduce it:
> 1) Clean install traffic monitor
> 2) Start tomcat and check the tomcat process ID
> 3) Add traffic monitor to traffic ops
> 4) Run traffic monitor config init perl script
> 5) Restart traffic monitor and check the tomcat process ID
> Check the process id, you will find the traffic monitor is not restarted at
> all. And the traffic monitor will be always in error status except kill it by
> "kill -9".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
