Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <27904953.1178142136265.JavaMail.jira@brutus>
Date: Wed, 2 May 2007 14:42:16 -0700 (PDT)
From: "Michael Bieniosek (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-1319) NPE in TaskLog.getTaskLogDir, as
 called from tasklog.jsp
In-Reply-To: <22096057.1178142015673.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493222 ] 

Michael Bieniosek commented on HADOOP-1319:
-------------------------------------------

The plaintext=true part seems crucial to the NPE.

> NPE in TaskLog.getTaskLogDir, as called from tasklog.jsp
> --------------------------------------------------------
>
>                 Key: HADOOP-1319
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1319
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.12.3
>            Reporter: Michael Bieniosek
>            Priority: Minor
>
> Calling TaskCompletionEvent.getTaskTrackerHttp() gives me an url that looks like http://tasktracker.host:50060/tasklog.jsp?plaintext=true&taskid=task_0264_m_000083_0&all=true.  If I try to access that URL, I get a Jetty 500 error.  In my tasktracker logs, I then see:
> 2007-05-02 21:32:16,107 WARN /: /tasklog.jsp?taskid=task_0261_m_000000_0&all=true&
> plaintext=true: 
> java.lang.NullPointerException
>         at org.apache.hadoop.mapred.TaskLog.getTaskLogDir(TaskLog.java:49)
>         at org.apache.hadoop.mapred.TaskLog.access$000(TaskLog.java:33)
>         at org.apache.hadoop.mapred.TaskLog$Reader.<init>(TaskLog.java:313)
>         at org.apache.hadoop.mapred.tasklog_jsp.printTaskLog(tasklog_jsp.java:26)
>         at org.apache.hadoop.mapred.tasklog_jsp._jspService(tasklog_jsp.java:232)
>         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(WebApplication
> Handler.java:475)
>         at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567
> )
>         at org.mortbay.http.HttpContext.handle(HttpContext.java:1565)
>         at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationCo
> ntext.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:24
> 4)
>         at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
>         at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.