ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prabhjyot Singh (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-18182) After the upgrade of jetty, zeppelin-view fails to load
Date Wed, 17 Aug 2016 11:35:21 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-18182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Prabhjyot Singh updated AMBARI-18182:
-------------------------------------
    Summary: After the upgrade of jetty, zeppelin-view fails to load  (was: Ambari server
start fails (become stopped) after upgrade with java.lang.NoSuchFieldError: IS_SECURITY_ENABLED)

> After the upgrade of jetty, zeppelin-view fails to load
> -------------------------------------------------------
>
>                 Key: AMBARI-18182
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18182
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views
>    Affects Versions: 2.4.0
>            Reporter: Prabhjyot Singh
>            Assignee: Prabhjyot Singh
>            Priority: Blocker
>             Fix For: trunk, 2.4.0
>
>
> Observed this issue after upgrade of Ambari server from 2.2.2.0 to 2.4.0.0 where after
running "ambari-server start" command, the logs throw below errors:
> {code}
> 05 Aug 2016 18:00:03,007 ERROR [main] AmbariServer:927 - Failed to run the Ambari Server
> 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.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:532)
> 	at org.eclipse.jetty.servlet.ServletHolder.doStart(ServletHolder.java:344)
> 	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> 	at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:793)
> 	at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:265)
> 	at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1242)
> 	at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:717)
> 	at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:494)
> 	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> 	at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
> 	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> 	at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
> 	at org.eclipse.jetty.server.Server.doStart(Server.java:282)
> 	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> 	at org.apache.ambari.server.controller.AmbariServer.run(AmbariServer.java:616)
> 	at org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:925)
> {code}
> [~jhurley] helped to look at the environment and mentioned that this is due to https://github.com/apache/ambari/commit/c03b6d4b01fbc336c296c9a1a92ca1308cba6ffc



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message