[
https://issues.apache.org/jira/browse/MAPREDUCE-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907717#action_12907717
]
Dan Adkins commented on MAPREDUCE-2058:
---------------------------------------
I have observed this in
https://svn.apache.org/repos/asf/hadoop/mapreduce/tr...@994941 as well as in
the recent hadoop-0.21.0 release.
> FairScheduler:NullPointerException in web interface when JobTracker not
> initialized
> -----------------------------------------------------------------------------------
>
> Key: MAPREDUCE-2058
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2058
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: contrib/fair-share
> Affects Versions: 0.22.0
> Reporter: Dan Adkins
>
> When I contact the jobtracker web interface prior to the job tracker being
> fully initialized (say, if hdfs is still in safe mode), I get the following
> error:
> 10/09/09 18:06:02 ERROR mortbay.log: /jobtracker.jsp
> java.lang.NullPointerException
> at
> org.apache.hadoop.mapred.FairScheduler.getJobs(FairScheduler.java:909)
> at
> org.apache.hadoop.mapred.JobTracker.getJobsFromQueue(JobTracker.java:4357)
> at
> org.apache.hadoop.mapred.JobTracker.getQueueInfoArray(JobTracker.java:4334)
> at
> org.apache.hadoop.mapred.JobTracker.getRootQueues(JobTracker.java:4295)
> at
> org.apache.hadoop.mapred.jobtracker_jsp.generateSummaryTable(jobtracker_jsp.java:44)
> at
> org.apache.hadoop.mapred.jobtracker_jsp._jspService(jobtracker_jsp.java:176)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1124)
> at
> org.apache.hadoop.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:857)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1115)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:361)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
> at
> org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
> 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:324)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
