[
https://issues.apache.org/jira/browse/TS-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726359#comment-14726359
]
Leif Hedstrom edited comment on TS-3882 at 9/1/15 10:51 PM:
------------------------------------------------------------
Perfect, thanks [~briang] That was always the intent, john initially did this
feature, so I'm guessing he missed a case where it's not hopping back. Also,
there's a similar issue with the dedicated thread pool for remap plugins,
TS-1590 :-).
was (Author: zwoop):
Perfect, thanks [~briang] That was always the intent, john initially did this
feature, so I'm guessing he missed a case where it's not hopping back.
> Crash caused by enabling dedicated DNS thread
> ---------------------------------------------
>
> Key: TS-3882
> URL: https://issues.apache.org/jira/browse/TS-3882
> Project: Traffic Server
> Issue Type: Bug
> Components: Core, DNS
> Reporter: Brian Geffon
> Assignee: Brian Geffon
>
> When enabling ``CONFIG proxy.config.dns.dedicated_thread INT 1`` we're
> observing a crash because apparently the continuation is called back while
> still on the DNS thread. This becomes a problem because when using shared
> server sessions 2 (per-thread sessions) it relies on a thread local that only
> exists on ET_NET / ET_SSL threads. The fix for this shouldn't be bad, we just
> need to make sure we pop over to a ET_NET thread when calling back the
> continuation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
