You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@htrace.apache.org by "Mike Drob (JIRA)" <ji...@apache.org> on 2016/04/15 19:33:25 UTC
[jira] [Created] (HTRACE-355) TraceRunnable and TraceCallable
should pull description from child thread instead of parent
Mike Drob created HTRACE-355:
--------------------------------
Summary: TraceRunnable and TraceCallable should pull description from child thread instead of parent
Key: HTRACE-355
URL: https://issues.apache.org/jira/browse/HTRACE-355
Project: HTrace
Issue Type: Bug
Components: core
Affects Versions: 4.1
Reporter: Mike Drob
Assignee: Mike Drob
Attachments: HTRACE-355.patch.txt
If a TraceRunnable or TraceCallable is passed a null scope name, then it will set the description to the current thread's name, which happens to be the parent thread. It would be much more useful to set the description to the child thread's name.
A nice side effect of this change is that we can add a version of {{tracer.newTraceExecutor}} that doesn't need to take a description for use by applications that take great care to name their threads in an informative manner.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)