[ 
https://issues.apache.org/jira/browse/HIVE-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748974#action_12748974
 ] 

Edward Capriolo commented on HIVE-752:
--------------------------------------

Even with the changes above HWI is having a hard time starting up. I will look 
into this.

{noformat}
[ecapri...@laptop1 dist]$ HADOOP_HOME=/home/ecapriolo/hadoop-0.20.0 bin/hive 
--service hwi
09/08/28 16:35:33 INFO hwi.HWIServer: HWI is starting up
09/08/28 16:35:33 FATAL hwi.HWIServer: HWI WAR file not found at 
${HIVE_HOME}/lib/hive-hwi.war
09/08/28 16:35:33 INFO mortbay.log: Logging to 
org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog
09/08/28 16:35:33 INFO mortbay.log: jetty-6.1.14
09/08/28 16:35:33 ERROR mortbay.log: Failed startup of context 
org.mortbay.jetty.webapp.webappcont...@e64686{/,null}
java.lang.NullPointerException
        at org.mortbay.resource.Resource.newResource(Resource.java:140)
        at org.mortbay.resource.Resource.newResource(Resource.java:120)
        at 
org.mortbay.jetty.webapp.WebAppContext.resolveWebApp(WebAppContext.java:885)
        at 
org.mortbay.jetty.webapp.WebAppContext.getWebInf(WebAppContext.java:793)
        at 
org.mortbay.jetty.webapp.WebInfConfiguration.configureClassLoader(WebInfConfiguration.java:62)
        at 
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:456)
        at 
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
        at 
org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
        at 
org.mortbay.jetty.handler.RequestLogHandler.doStart(RequestLogHandler.java:115)
        at 
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
        at 
org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
        at org.mortbay.jetty.Server.doStart(Server.java:222)
        at 
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
        at org.apache.hadoop.hive.hwi.HWIServer.start(HWIServer.java:79)
        at org.apache.hadoop.hive.hwi.HWIServer.main(HWIServer.java:108)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.apache.hadoop.util.RunJar.main(RunJar.java:156)
09/08/28 16:35:33 INFO mortbay.log: Started [email protected]:9999


{noformat}

> Encountered ClassNotFound exception when trying HWI server
> ----------------------------------------------------------
>
>                 Key: HIVE-752
>                 URL: https://issues.apache.org/jira/browse/HIVE-752
>             Project: Hadoop Hive
>          Issue Type: Bug
>          Components: Clients
>         Environment: Hadoop 0.18.3
>            Reporter: Venkat Ramachandran
>
> Encountered ClassNotFound exception (for class: 
> org.apache.jetty.hive.shims.Jetty18Shims) when trying to start HWI server on 
> Hadoop 18.
> It appears that the class ShimLoader 
> (org.apache.hadoop.hive.shims.ShimLoader) is referring to incorrect classes 
> as below:
> static {
>     JETTY_SHIM_CLASSES.put("0.17", 
> "org.apache.jetty.hive.shims.Jetty17Shims");
>     JETTY_SHIM_CLASSES.put("0.18", 
> "org.apache.jetty.hive.shims.Jetty18Shims");
>     JETTY_SHIM_CLASSES.put("0.19", 
> "org.apache.jetty.hive.shims.Jetty19Shims");
>     JETTY_SHIM_CLASSES.put("0.20", 
> "org.apache.jetty.hive.shims.Jetty20Shims");
>   }
> however, I think it should be as below:
>  static 
>   {
>         JETTY_SHIM_CLASSES.put("0.17", 
> "org.apache.hadoop.hive.shims.Jetty17Shims");
>         JETTY_SHIM_CLASSES.put("0.18", 
> "org.apache.hadoop.hive.shims.Jetty18Shims");
>         JETTY_SHIM_CLASSES.put("0.19", 
> "org.apache.hadoop.hive.shims.Jetty19Shims");
>         JETTY_SHIM_CLASSES.put("0.20", 
> "org.apache.hadoop.hive.shims.Jetty20Shims");
>   } 
> Wondering if anybody else encountered this.

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

Reply via email to