[
https://issues.apache.org/jira/browse/HADOOP-10106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao updated HADOOP-10106:
-------------------------------
Resolution: Fixed
Fix Version/s: 2.4.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
I've committed this to trunk and branch-2.
[~mingma], currently I could not add your name to the contributor list (got
some error msg in the jira system) so I could not assign this jira to you. I
will try it again and update the jira information later.
> 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
> Reporter: Ming Ma
> Priority: Minor
> Fix For: 2.4.0
>
> Attachments: hadoop_10106_trunk.patch, hadoop_10106_trunk_2.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.4#6159)
