[
https://issues.apache.org/jira/browse/YARN-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13643626#comment-13643626
]
Hudson commented on YARN-363:
-----------------------------
Integrated in Hadoop-Yarn-trunk #196 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/196/])
YARN-363. Add webapps/proxy directory without which YARN proxy-server fails
when started in stand-alone mode. Contributed by Kenji Kikushima. (Revision
1476330)
Result = SUCCESS
vinodkv :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1476330
Files :
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-web-proxy/src/test/java/org/apache/hadoop/yarn/server/webproxy/TestWebAppProxyServer.java
> yarn proxyserver fails to find webapps/proxy directory on startup
> -----------------------------------------------------------------
>
> Key: YARN-363
> URL: https://issues.apache.org/jira/browse/YARN-363
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 0.23.6
> Reporter: Jason Lowe
> Assignee: Kenji Kikushima
> Fix For: 2.0.5-beta, 0.23.8
>
> Attachments: YARN-363.patch
>
>
> Starting up the proxy server fails with this error:
> {noformat}
> 2013-01-29 17:37:41,357 FATAL webproxy.WebAppProxy
> (WebAppProxy.java:start(99)) - Could not start proxy web server
> java.io.FileNotFoundException: webapps/proxy not found in CLASSPATH
> at org.apache.hadoop.http.HttpServer.getWebAppsPath(HttpServer.java:533)
> at org.apache.hadoop.http.HttpServer.<init>(HttpServer.java:225)
> at org.apache.hadoop.http.HttpServer.<init>(HttpServer.java:164)
> at
> org.apache.hadoop.yarn.server.webproxy.WebAppProxy.start(WebAppProxy.java:90)
> at
> org.apache.hadoop.yarn.service.CompositeService.start(CompositeService.java:68)
> at
> org.apache.hadoop.yarn.server.webproxy.WebAppProxyServer.main(WebAppProxyServer.java:94)
> {noformat}
--
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
