You might be able to fix this by using a JDK/SDK not only a jre.

On Wed, Aug 21, 2013 at 1:38 AM, Bing Li (JIRA) <j...@apache.org> wrote:

> Bing Li created HIVE-5132:
> -----------------------------
>
>              Summary: Can't access to hwi
>                  Key: HIVE-5132
>                  URL: https://issues.apache.org/jira/browse/HIVE-5132
>              Project: Hive
>           Issue Type: Bug
>     Affects Versions: 0.11.0, 0.10.0
>          Environment: JDK1.6, hadoop 2.0.4-alpha
>             Reporter: Bing Li
>             Priority: Critical
>
>
> I want to use hwi to submit hive queries, but after start hwi
> successfully, I can't open the web page of it.
>
> I noticed that someone also met the same issue in hive-0.10.
>
> Reproduce steps:
> --------------------------
> 1. start hwi
> bin/hive --config $HIVE_CONF_DIR --service hwi
>
> 2. access to http://<hive_hwi_node>:9999/hwi via browser
>
> got the following error message:
>
> HTTP ERROR 500
> Problem accessing /hwi/. Reason:
>
>     No Java compiler available
>
> Caused by:
> java.lang.IllegalStateException: No Java compiler available
>         at
> org.apache.jasper.JspCompilationContext.createCompiler(JspCompilationContext.java:225)
>         at
> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:560)
>         at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:299)
>         at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:315)
>         at
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
>         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.servlet.Dispatcher.forward(Dispatcher.java:327)
>         at
> org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)
>         at
> org.mortbay.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:503)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>         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)
>
>
>
> --
> 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
>

Reply via email to