[
https://issues.apache.org/jira/browse/ZOOKEEPER-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642564#action_12642564
]
Patrick Hunt commented on ZOOKEEPER-207:
----------------------------------------
Agreed. I fixed a bunch of these in 3.0.0 but I probably didn't get everything.
Additionally if the thread is in some way connected to a particular host or
host/port (etc...) this type of information would be great to have in the name.
You may also want to look at Nested Diagnostic Contexts support in log4j:
http://logging.apache.org/log4j/1.2/manual.html
Doesn't quite work for us in things like client's sendthread (I tried it once a
while back), but may be better suited for server code.
> All the threads should have names so that its easier to see throguh a stack
> trace.
> ----------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-207
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-207
> Project: Zookeeper
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.0.0
> Reporter: Mahadev konar
> Assignee: Mahadev konar
> Priority: Minor
> Fix For: 3.1.0
>
>
> the threads should have names so that its easier to look through the stack
> trace.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
