[jira] [Commented] (HADOOP-10106) Incorrect thread name in RPC log messages

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on HADOOP-10106:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12614181/hadoop_10106_trunk.patch
  against trunk revision .

    {color:red}-1 patch{color}.  Trunk compilation may be broken.

Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3291//console

This message is automatically generated.

> Incorrect thread name in RPC log messages
> -----------------------------------------
>
>                 Key: HADOOP-10106
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10106
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 3.0.0, 2.2.0
>            Reporter: Ming Ma
>            Priority: Minor
>             Fix For: 3.0.0, 2.2.1
>
>         Attachments: hadoop_10106_trunk.patch
>
>
> INFO org.apache.hadoop.ipc.Server: IPC Server listener on 8020: readAndProcess from client 10.115.201.46 threw exception org.apache.hadoop.ipc.RpcServerException: Unknown out of band call #-2147483647
> This is thrown by a reader thread, so the message should be like
> INFO org.apache.hadoop.ipc.Server: Socket Reader #1 for port 8020: readAndProcess from client 10.115.201.46 threw exception org.apache.hadoop.ipc.RpcServerException: Unknown out of band call #-2147483647
> Another example is Responder.processResponse, which can also be called by handler thread. When that happend, the thread name should be the handler thread, not the responder thread.



--
This message was sent by Atlassian JIRA
(v6.1#6144)