[
https://issues.apache.org/jira/browse/TS-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15270268#comment-15270268
]
ASF subversion and git services commented on TS-4387:
-----------------------------------------------------
Commit f96c1f505564280b3f12a98c3ae7abc33b73b168 in trafficserver's branch
refs/heads/master from [~shenzhang920]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=f96c1f5 ]
TS-4387: When calling TSContSchedule()/TSContScheduleEvery(), the passed
in parameter TSCont have to have MUTEX; otherwise if we call
TSContSchedule()/TSContScheduleEvery() more than once using same TSCont,
only the first call will take effect; all the following schedule are
ignored due to MUTEX issue.
This closes #603
> Add enforcement of TSCont having MUTEX when passed to
> TSContSchedule()/TSContScheduleEvery()
> --------------------------------------------------------------------------------------------
>
> Key: TS-4387
> URL: https://issues.apache.org/jira/browse/TS-4387
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Shen Zhang
> Assignee: Brian Geffon
> Fix For: 7.0.0
>
>
> When calling TSContSchedule()/TSContScheduleEvery(), the passed in parameter
> TSCont have to have MUTEX; otherwise if we call
> TSContSchedule()/TSContScheduleEvery() more than once using same TSCont, only
> the first call will take effect; all the following schedule are ignored due
> to MUTEX issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
