You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tajo.apache.org by "Jinho Kim (JIRA)" <ji...@apache.org> on 2013/08/16 10:42:51 UTC
[jira] [Commented] (TAJO-129) Enable the constructor of
NettyServerBase to take service name
[ https://issues.apache.org/jira/browse/TAJO-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742038#comment-13742038 ]
Jinho Kim commented on TAJO-129:
--------------------------------
+1
great work! I've verified 'mvn clean install'.
> Enable the constructor of NettyServerBase to take service name
> --------------------------------------------------------------
>
> Key: TAJO-129
> URL: https://issues.apache.org/jira/browse/TAJO-129
> Project: Tajo
> Issue Type: Task
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Fix For: 0.2-incubating
>
> Attachments: TAJO-129_2.patch, TAJO-129.patch
>
>
> The rpc server class NettyServerBase does not take service name. So, it outputs the info log messages as follows:
> {noformat}
> 2013-08-14 18:02:43,423 INFO rpc.NettyServerBase (NettyServerBase.java:start(84)) - RpcServer on /127.0.0.1:56135
> {noformat}
> But, this way makes debugging very hard because users cannot recognize the port bound to any service. We need to enable the constructor of NettyServerBase to take service name and provide some access methods.
--
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