You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Deepesh Khandelwal (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/31 00:31:28 UTC
[jira] [Resolved] (HBASE-5683) Inconsistent behavior of bin/hbase
scripts on different shell
[ https://issues.apache.org/jira/browse/HBASE-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepesh Khandelwal resolved HBASE-5683.
---------------------------------------
Resolution: Duplicate
Duplicate of HBASE-5286.
> Inconsistent behavior of bin/hbase scripts on different shell
> -------------------------------------------------------------
>
> Key: HBASE-5683
> URL: https://issues.apache.org/jira/browse/HBASE-5683
> Project: HBase
> Issue Type: Bug
> Components: scripts
> Affects Versions: 0.92.0
> Environment: GNU bash, version 3.2.51(1)-release (x86_64-suse-linux-gnu)
> Reporter: Deepesh Khandelwal
>
> When starting the hbase on the specific shell, observed that the HBase webapp at port 60010 was throwing a NOT FOUND error. The HBase server log was showing the following error:
> 2012-03-30 19:29:32,396 WARN org.mortbay.log: failed ContextHandlerCollection@67e2c841: java.lang.NoSuchFieldError: IS_SECURITY_ENABLED
> 2012-03-30 19:29:32,396 ERROR org.mortbay.log: Error starting handlers
> java.lang.NoSuchFieldError: IS_SECURITY_ENABLED
> at org.apache.jasper.compiler.JspRuntimeContext.<init>(JspRuntimeContext.java:197)
> at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:150)
> at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:440)
> at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263)
> at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:736)
> at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
> at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1282)
> at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:518)
> at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499)
> at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
> at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
> 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:224)
> at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.apache.hadoop.http.HttpServer.start(HttpServer.java:617)
> at org.apache.hadoop.hbase.master.HMaster.startServiceThreads(HMaster.java:758)
> at org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:479)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:334)
> at java.lang.Thread.run(Thread.java:662)
> The problem is apparently to do with the current classpath where we are using * to add multiple jars on the classpath. After following the same convention as bin/hadoop to add the individual jars, the errors are gone and the HBase webapp loads correctly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira