[jira] [Updated] (TAJO-129) Enable the constructor of NettyServerBase to take service name

["Hyunsik Choi (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAJO-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyunsik Choi updated TAJO-129:
------------------------------

    Attachment: TAJO-129.patch

This patch does as follows:
 * Enable NettyServerBase constructor to take a service name,
 * Improve NettyServerBase to write a log message with a given service name.
 * Improve NettyServerBase to obtain an arbitrary port number from a port range when the server address port is set to 0.
 * Fix rpc unit tests not to print error messages.
 * Add some useful util methods to tajo.util.NetUtils.
 * NettyServerBase returns incorrect listen address when the server binds to "0.0.0.0". tajo.util.NetUtils.getConnectAddress can change such an address to a default host name. I borrowed it from Hadoop's NetUtils.
                
> 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
>         Attachments: 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