You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hive.apache.org by Krish Khambadkone <kk...@apple.com> on 2011/09/16 02:40:25 UTC
ExecDriver.runningJobKillURIs is not visible
I am using Hive 0.70. When I click on the "List Running Jobs" under Administration in the Hive GUI, I get this exception stack trace.
HTTP ERROR 500
Problem accessing /hwi/admin_list_jobs.jsp. Reason:
Unable to compile class for JSP
An error occurred at line: 40 in the jsp file: /admin_list_jobs.jsp
Generated servlet error:
The field ExecDriver.runningJobKillURIs is not visible
An error occurred at line: 43 in the jsp file: /admin_list_jobs.jsp
Generated servlet error:
The field ExecDriver.runningJobKillURIs is not visible
Caused by:
org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred at line: 40 in the jsp file: /admin_list_jobs.jsp
Generated servlet error:
The field ExecDriver.runningJobKillURIs is not visible
An error occurred at line: 43 in the jsp file: /admin_list_jobs.jsp
Generated servlet error:
The field ExecDriver.runningJobKillURIs is not visible
at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84)
at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:328)
at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:409)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:288)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:267)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:255)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:563)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:293)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
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.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.handler.RequestLogHandler.handle(RequestLogHandler.java:49)
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.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Re: ExecDriver.runningJobKillURIs is not visible
Posted by Edward Capriolo <ed...@gmail.com>.
There is no fix. The page is removed in new versions. This information is
really just a subset of information you could find from the hadoop
jobtracker. It was nice because you were sure which jobs belonged to hive.
I write my hive select queries with some bogus comments like so.
select /* jid=5 */
This makes them easy to identify while looking at the job tracker.
Edward
On Fri, Sep 16, 2011 at 12:18 AM, Krish Khambadkone
<kk...@apple.com>wrote:
> Is there anyway to fix this in 0.70 w/o having to upgrade to 0.80.
>
> --Krish.
>
> On Sep 15, 2011, at 6:00 PM, Edward Capriolo wrote:
>
> This was removed in 0.8.X because as you pointed out the function is no
> longer visible.
>
> On Thu, Sep 15, 2011 at 8:40 PM, Krish Khambadkone <kkhambadkone@apple.com
> > wrote:
>
>> I am using Hive 0.70. When I click on the "List Running Jobs<http://17.209.23.178:9999/hwi/admin_list_jobs.jsp>"
>> under Administration in the Hive GUI, I get this exception stack trace.
>>
>>
>> HTTP ERROR 500
>>
>> Problem accessing /hwi/admin_list_jobs.jsp. Reason:
>>
>> Unable to compile class for JSP
>>
>> An error occurred at line: 40 in the jsp file: /admin_list_jobs.jsp
>> Generated servlet error:
>> The field ExecDriver.runningJobKillURIs is not visible
>>
>> An error occurred at line: 43 in the jsp file: /admin_list_jobs.jsp
>> Generated servlet error:
>> The field ExecDriver.runningJobKillURIs is not visible
>>
>>
>>
>> Caused by:
>>
>> org.apache.jasper.JasperException: Unable to compile class for JSP
>>
>> An error occurred at line: 40 in the jsp file: /admin_list_jobs.jsp
>> Generated servlet error:
>> The field ExecDriver.runningJobKillURIs is not visible
>>
>> An error occurred at line: 43 in the jsp file: /admin_list_jobs.jsp
>> Generated servlet error:
>> The field ExecDriver.runningJobKillURIs is not visible
>>
>>
>> at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84)
>> at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:328)
>> at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:409)
>> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:288)
>> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:267)
>> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:255)
>> at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:563)
>> at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:293)
>> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
>> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>> at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
>> at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
>> 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.HandlerWrapper.handle(HandlerWrapper.java:152)
>> at org.mortbay.jetty.handler.RequestLogHandler.handle(RequestLogHandler.java:49)
>> 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.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
>> at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
>>
>>
>>
>
>
Re: ExecDriver.runningJobKillURIs is not visible
Posted by Krish Khambadkone <kk...@apple.com>.
Is there anyway to fix this in 0.70 w/o having to upgrade to 0.80.
--Krish.
On Sep 15, 2011, at 6:00 PM, Edward Capriolo wrote:
> This was removed in 0.8.X because as you pointed out the function is no longer visible.
>
> On Thu, Sep 15, 2011 at 8:40 PM, Krish Khambadkone <kk...@apple.com> wrote:
> I am using Hive 0.70. When I click on the "List Running Jobs" under Administration in the Hive GUI, I get this exception stack trace.
>
>
> HTTP ERROR 500
>
> Problem accessing /hwi/admin_list_jobs.jsp. Reason:
>
> Unable to compile class for JSP
>
> An error occurred at line: 40 in the jsp file: /admin_list_jobs.jsp
> Generated servlet error:
> The field ExecDriver.runningJobKillURIs is not visible
>
> An error occurred at line: 43 in the jsp file: /admin_list_jobs.jsp
> Generated servlet error:
> The field ExecDriver.runningJobKillURIs is not visible
>
>
> Caused by:
>
> org.apache.jasper.JasperException: Unable to compile class for JSP
>
> An error occurred at line: 40 in the jsp file: /admin_list_jobs.jsp
> Generated servlet error:
> The field ExecDriver.runningJobKillURIs is not visible
>
> An error occurred at line: 43 in the jsp file: /admin_list_jobs.jsp
> Generated servlet error:
> The field ExecDriver.runningJobKillURIs is not visible
>
>
> at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84)
> at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:328)
> at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:409)
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:288)
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:267)
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:255)
> at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:563)
> at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:293)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
> at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
> 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.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.handler.RequestLogHandler.handle(RequestLogHandler.java:49)
> 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.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
> at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
>
>
Re: ExecDriver.runningJobKillURIs is not visible
Posted by Edward Capriolo <ed...@gmail.com>.
This was removed in 0.8.X because as you pointed out the function is no
longer visible.
On Thu, Sep 15, 2011 at 8:40 PM, Krish Khambadkone
<kk...@apple.com>wrote:
> I am using Hive 0.70. When I click on the "List Running Jobs<http://17.209.23.178:9999/hwi/admin_list_jobs.jsp>"
> under Administration in the Hive GUI, I get this exception stack trace.
>
>
> HTTP ERROR 500
>
> Problem accessing /hwi/admin_list_jobs.jsp. Reason:
>
> Unable to compile class for JSP
>
> An error occurred at line: 40 in the jsp file: /admin_list_jobs.jsp
> Generated servlet error:
> The field ExecDriver.runningJobKillURIs is not visible
>
> An error occurred at line: 43 in the jsp file: /admin_list_jobs.jsp
> Generated servlet error:
> The field ExecDriver.runningJobKillURIs is not visible
>
>
>
> Caused by:
>
> org.apache.jasper.JasperException: Unable to compile class for JSP
>
> An error occurred at line: 40 in the jsp file: /admin_list_jobs.jsp
> Generated servlet error:
> The field ExecDriver.runningJobKillURIs is not visible
>
> An error occurred at line: 43 in the jsp file: /admin_list_jobs.jsp
> Generated servlet error:
> The field ExecDriver.runningJobKillURIs is not visible
>
>
> at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84)
> at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:328)
> at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:409)
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:288)
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:267)
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:255)
> at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:563)
> at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:293)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
> at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
> 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.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.handler.RequestLogHandler.handle(RequestLogHandler.java:49)
> 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.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
> at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
>
>
>