hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-749) The jobfailures.jsp gets a NullPointerException after a task tracker has been lost
Date Mon, 27 Nov 2006 21:41:22 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-749?page=all ]

Owen O'Malley updated HADOOP-749:
---------------------------------

    Attachment: jsp-null.patch

This patch puts a check for taskTracker == null into the jsp before using it to build a link
for the user logs.

> The jobfailures.jsp gets a NullPointerException after a task tracker has been lost
> ----------------------------------------------------------------------------------
>
>                 Key: HADOOP-749
>                 URL: http://issues.apache.org/jira/browse/HADOOP-749
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.8.0
>            Reporter: Owen O'Malley
>         Assigned To: Owen O'Malley
>             Fix For: 0.9.0
>
>         Attachments: jsp-null.patch
>
>
> The job tracker gets a NullPointerException:
> 2006-11-27 06:59:25,148 WARN /: /jobfailures.jsp?jobid=job_0001&kind=map:
> java.lang.NullPointerException
>         at org.apache.hadoop.mapred.jobfailures_jsp.printFailedAttempts(jobfailu
> res_jsp.java:57)
>         at org.apache.hadoop.mapred.jobfailures_jsp.printFailures(jobfailures_js
> p.java:103)
>         at org.apache.hadoop.mapred.jobfailures_jsp._jspService(jobfailures_jsp.
> java:168)
>         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>         at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:427
> )
>         at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicati
> onHandler.java:475)
>         at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:5
> 67)
>         at org.mortbay.http.HttpContext.handle(HttpContext.java:1565)
>         at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplication
> Context.java:635)
>         at org.mortbay.http.HttpContext.handle(HttpContext.java:1517)
>         at org.mortbay.http.HttpServer.service(HttpServer.java:954)
>         at org.mortbay.http.HttpConnection.service(HttpConnection.java:814)
>         at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:981)
>         at org.mortbay.http.HttpConnection.handle(HttpConnection.java:831)
>         at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:
> 244)
>         at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
>         at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
> when there is a lost task tracker. Since the task tracker was lost, when the jsp tries
to get the task tracker object for that task, it gets a null value. The jsp needs to protect
itself from nulls.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message