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

Alan M. Carroll commented on TS-4966:
-------------------------------------

There are two issues here. One is that the thread for the lifecycle callbacks 
for plugin messages should be an {{EThread}} to make this easier. This thread 
is started as a special case via {{startProcessManager::start}}.

The other issue is why {{PLUGIN_FORCE_SCOPED_MUTEX}} locks the mutex. I can see 
no reason to do that, since the continuation is guaranteed to be called in a 
different scope and the lock is not required to be held to schedule the 
continuation.

> Debug asserts fail when trying to schedule a continuation from a lifecycle 
> plugin message hook.
> -----------------------------------------------------------------------------------------------
>
>                 Key: TS-4966
>                 URL: https://issues.apache.org/jira/browse/TS-4966
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Plugins
>            Reporter: Alan M. Carroll
>
> The plugin message callback for the lifecycle hook is called from a special 
> core thread which is not an {{EThread}}. Because of this debug assertions 
> fail in {{TSContSchedule}} (and other API calls) because mutex operations 
> fail due to the lack of {{EThread}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to