[jira] [Commented] (MAPREDUCE-4927) Historyserver 500 error due to NPE when accessing specific counters page for failed job
[ https://issues.apache.org/jira/browse/MAPREDUCE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661331#comment-13661331 ] Hudson commented on MAPREDUCE-4927: --- Integrated in Hadoop-Yarn-trunk #213 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/213/]) MAPREDUCE-4927. Historyserver 500 error due to NPE when accessing specific counters page for failed job. Contributed by Ashwin Shankar (Revision 1483974) Result = FAILURE jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1483974 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/webapp/SingleCounterBlock.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/webapp/TestAMWebApp.java Historyserver 500 error due to NPE when accessing specific counters page for failed job --- Key: MAPREDUCE-4927 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4927 Project: Hadoop Map/Reduce Issue Type: Bug Components: jobhistoryserver Affects Versions: 2.0.3-alpha, 0.23.6 Reporter: Jason Lowe Assignee: Ashwin Shankar Fix For: 2.0.5-beta, 0.23.8 Attachments: MAPREDUCE-4927.txt Went to the historyserver page for a job that failed and examined the counters page. When I clicked on a specific counter, the historyserver returned a 500 error. The historyserver logs showed it encountered an NPE error, full traceback to follow. -- 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
[jira] [Commented] (MAPREDUCE-4927) Historyserver 500 error due to NPE when accessing specific counters page for failed job
[ https://issues.apache.org/jira/browse/MAPREDUCE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661350#comment-13661350 ] Hudson commented on MAPREDUCE-4927: --- Integrated in Hadoop-Hdfs-0.23-Build #611 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/611/]) svn merge -c 1483974 FIXES: MAPREDUCE-4927. Historyserver 500 error due to NPE when accessing specific counters page for failed job. Contributed by Ashwin Shankar (Revision 1483978) Result = SUCCESS jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1483978 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/webapp/SingleCounterBlock.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/webapp/TestAMWebApp.java Historyserver 500 error due to NPE when accessing specific counters page for failed job --- Key: MAPREDUCE-4927 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4927 Project: Hadoop Map/Reduce Issue Type: Bug Components: jobhistoryserver Affects Versions: 2.0.3-alpha, 0.23.6 Reporter: Jason Lowe Assignee: Ashwin Shankar Fix For: 2.0.5-beta, 0.23.8 Attachments: MAPREDUCE-4927.txt Went to the historyserver page for a job that failed and examined the counters page. When I clicked on a specific counter, the historyserver returned a 500 error. The historyserver logs showed it encountered an NPE error, full traceback to follow. -- 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
[jira] [Commented] (MAPREDUCE-4927) Historyserver 500 error due to NPE when accessing specific counters page for failed job
[ https://issues.apache.org/jira/browse/MAPREDUCE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661354#comment-13661354 ] Hudson commented on MAPREDUCE-4927: --- Integrated in Hadoop-Hdfs-trunk #1402 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1402/]) MAPREDUCE-4927. Historyserver 500 error due to NPE when accessing specific counters page for failed job. Contributed by Ashwin Shankar (Revision 1483974) Result = FAILURE jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1483974 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/webapp/SingleCounterBlock.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/webapp/TestAMWebApp.java Historyserver 500 error due to NPE when accessing specific counters page for failed job --- Key: MAPREDUCE-4927 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4927 Project: Hadoop Map/Reduce Issue Type: Bug Components: jobhistoryserver Affects Versions: 2.0.3-alpha, 0.23.6 Reporter: Jason Lowe Assignee: Ashwin Shankar Fix For: 2.0.5-beta, 0.23.8 Attachments: MAPREDUCE-4927.txt Went to the historyserver page for a job that failed and examined the counters page. When I clicked on a specific counter, the historyserver returned a 500 error. The historyserver logs showed it encountered an NPE error, full traceback to follow. -- 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
[jira] [Commented] (MAPREDUCE-4927) Historyserver 500 error due to NPE when accessing specific counters page for failed job
[ https://issues.apache.org/jira/browse/MAPREDUCE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661359#comment-13661359 ] Hudson commented on MAPREDUCE-4927: --- Integrated in Hadoop-Mapreduce-trunk #1429 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1429/]) MAPREDUCE-4927. Historyserver 500 error due to NPE when accessing specific counters page for failed job. Contributed by Ashwin Shankar (Revision 1483974) Result = FAILURE jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1483974 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/webapp/SingleCounterBlock.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/webapp/TestAMWebApp.java Historyserver 500 error due to NPE when accessing specific counters page for failed job --- Key: MAPREDUCE-4927 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4927 Project: Hadoop Map/Reduce Issue Type: Bug Components: jobhistoryserver Affects Versions: 2.0.3-alpha, 0.23.6 Reporter: Jason Lowe Assignee: Ashwin Shankar Fix For: 2.0.5-beta, 0.23.8 Attachments: MAPREDUCE-4927.txt Went to the historyserver page for a job that failed and examined the counters page. When I clicked on a specific counter, the historyserver returned a 500 error. The historyserver logs showed it encountered an NPE error, full traceback to follow. -- 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
[jira] [Commented] (MAPREDUCE-4927) Historyserver 500 error due to NPE when accessing specific counters page for failed job
[ https://issues.apache.org/jira/browse/MAPREDUCE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13660978#comment-13660978 ] Jason Lowe commented on MAPREDUCE-4927: --- +1, lgtm. Historyserver 500 error due to NPE when accessing specific counters page for failed job --- Key: MAPREDUCE-4927 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4927 Project: Hadoop Map/Reduce Issue Type: Bug Components: jobhistoryserver Affects Versions: 2.0.3-alpha, 0.23.6 Reporter: Jason Lowe Assignee: Ashwin Shankar Attachments: MAPREDUCE-4927.txt Went to the historyserver page for a job that failed and examined the counters page. When I clicked on a specific counter, the historyserver returned a 500 error. The historyserver logs showed it encountered an NPE error, full traceback to follow. -- 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
[jira] [Commented] (MAPREDUCE-4927) Historyserver 500 error due to NPE when accessing specific counters page for failed job
[ https://issues.apache.org/jira/browse/MAPREDUCE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661017#comment-13661017 ] Hudson commented on MAPREDUCE-4927: --- Integrated in Hadoop-trunk-Commit #3766 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/3766/]) MAPREDUCE-4927. Historyserver 500 error due to NPE when accessing specific counters page for failed job. Contributed by Ashwin Shankar (Revision 1483974) Result = SUCCESS jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1483974 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/webapp/SingleCounterBlock.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/webapp/TestAMWebApp.java Historyserver 500 error due to NPE when accessing specific counters page for failed job --- Key: MAPREDUCE-4927 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4927 Project: Hadoop Map/Reduce Issue Type: Bug Components: jobhistoryserver Affects Versions: 2.0.3-alpha, 0.23.6 Reporter: Jason Lowe Assignee: Ashwin Shankar Attachments: MAPREDUCE-4927.txt Went to the historyserver page for a job that failed and examined the counters page. When I clicked on a specific counter, the historyserver returned a 500 error. The historyserver logs showed it encountered an NPE error, full traceback to follow. -- 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
[jira] [Commented] (MAPREDUCE-4927) Historyserver 500 error due to NPE when accessing specific counters page for failed job
[
https://issues.apache.org/jira/browse/MAPREDUCE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13660126#comment-13660126
]
Hadoop QA commented on MAPREDUCE-4927:
--
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12583567/MAPREDUCE-4927.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3649//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3649//console
This message is automatically generated.
Historyserver 500 error due to NPE when accessing specific counters page for
failed job
---
Key: MAPREDUCE-4927
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4927
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: jobhistoryserver
Affects Versions: 2.0.3-alpha, 0.23.6
Reporter: Jason Lowe
Assignee: Ashwin Shankar
Attachments: MAPREDUCE-4927.txt
Went to the historyserver page for a job that failed and examined the
counters page. When I clicked on a specific counter, the historyserver
returned a 500 error. The historyserver logs showed it encountered an NPE
error, full traceback to follow.
--
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
[jira] [Commented] (MAPREDUCE-4927) Historyserver 500 error due to NPE when accessing specific counters page for failed job
[
https://issues.apache.org/jira/browse/MAPREDUCE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13547215#comment-13547215
]
Jason Lowe commented on MAPREDUCE-4927:
---
Traceback from historyserver log:
{noformat}
2013-01-08 20:18:06,156 ERROR [1936114592@qtp-528534273-7] webapp.Dispatcher
(Dispatcher.java:service(159)) - error handling URI:
/jobhistory/singlejobcounter/job_1357675842476_0001/org.apache.hadoop.mapreduce.TaskCounter/GC_TIME_MILLIS
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.hadoop.yarn.webapp.Dispatcher.service(Dispatcher.java:150)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:263)
at
com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:178)
at
com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
at
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:62)
at
com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:900)
at
com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:834)
at
com.sun.jersey.spi.container.servlet.ServletContainer.doFilter(ServletContainer.java:795)
at
com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
at
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
at
com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118)
at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
at
org.apache.hadoop.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:109)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
at
org.apache.hadoop.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1072)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
at org.apache.hadoop.http.NoCacheFilter.doFilter(NoCacheFilter.java:45)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
at org.apache.hadoop.http.NoCacheFilter.doFilter(NoCacheFilter.java:45)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Caused by: com.google.inject.ProvisionException: Guice provision errors:
1) Error injecting constructor, java.lang.NullPointerException
at
org.apache.hadoop.mapreduce.v2.app.webapp.SingleCounterBlock.init(SingleCounterBlock.java:56)
while locating org.apache.hadoop.mapreduce.v2.app.webapp.SingleCounterBlock
1 error
at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:987)
at
com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1013)
at org.apache.hadoop.yarn.webapp.View.getInstance(View.java:106)
at org.apache.hadoop.yarn.webapp.View.render(View.java:233)
at
org.apache.hadoop.yarn.webapp.view.HtmlPage$Page.subView(HtmlPage.java:47)
at
