[
https://issues.apache.org/jira/browse/CASSANDRA-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446533#comment-13446533
]
Hudson commented on CASSANDRA-4599:
-----------------------------------
Integrated in Cassandra #1988 (See
[https://builds.apache.org/job/Cassandra/1988/])
fix for logging events' correct thread name; patch by yukim reviewed by
David Alves for CASSANDRA-4599 (Revision
e49d140bb72264a503a634d5603c25766c78e50d)
Result = ABORTED
yukim :
Files :
* src/java/org/apache/cassandra/tracing/TracingAppender.java
> Event tracing always records thread name as 'TracingStage'
> ----------------------------------------------------------
>
> Key: CASSANDRA-4599
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4599
> Project: Cassandra
> Issue Type: Bug
> Reporter: Yuki Morishita
> Assignee: Yuki Morishita
> Priority: Trivial
> Fix For: 1.2.0 beta 1
>
> Attachments: 4599.txt
>
>
> Since LoggingEvent#getThreadName gets current thread name when accessed, name
> of tracing thread ('TracingStage') is always logged to events CF.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
