[
https://issues.apache.org/jira/browse/HDFS-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292183#comment-13292183
]
Hudson commented on HDFS-3490:
------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #2413 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2413/])
HDFS-3490. DatanodeWebHdfsMethods throws NullPointerException if
NamenodeRpcAddressParam is not set. (Revision 1348287)
Result = SUCCESS
szetszwo :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1348287
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/web/resources/DatanodeWebHdfsMethods.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/web/resources/NamenodeWebHdfsMethods.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/web/resources/InetSocketAddressParam.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/web/resources/LongParam.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/web/TestWebHdfsFileSystemContract.java
> DN WebHDFS methods throw NPE if Namenode RPC address param not specified
> ------------------------------------------------------------------------
>
> Key: HDFS-3490
> URL: https://issues.apache.org/jira/browse/HDFS-3490
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: data-node
> Affects Versions: 2.0.0-alpha
> Reporter: Todd Lipcon
> Assignee: Tsz Wo (Nicholas), SZE
> Priority: Minor
> Fix For: 2.0.1-alpha
>
> Attachments: h3490_20120605.patch, h3490_20120606.patch
>
>
> If NamenodeRpcAddressParam is not passed to the datanode webhdfs methods, an
> NPE will be generated trying to use it. We should check the parameter and
> throw a more appropriate error message when it is missing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
