Return-Path: <issues-return-23223-archive-asf-public=cust-asf.ponee.io@ambari.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 1FADB200B65
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Wed, 17 Aug 2016 13:31:22 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 1E5BC160ABB; Wed, 17 Aug 2016 11:31:22 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 64258160A86
	for <archive-asf-public@cust-asf.ponee.io>; Wed, 17 Aug 2016 13:31:21 +0200 (CEST)
Received: (qmail 96692 invoked by uid 500); 17 Aug 2016 11:31:20 -0000
Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@ambari.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@ambari.apache.org>
List-Post: <mailto:issues@ambari.apache.org>
List-Id: <issues.ambari.apache.org>
Reply-To: dev@ambari.apache.org
Delivered-To: mailing list issues@ambari.apache.org
Received: (qmail 96663 invoked by uid 99); 17 Aug 2016 11:31:20 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Aug 2016 11:31:20 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 7D4032C0032
	for <issues@ambari.apache.org>; Wed, 17 Aug 2016 11:31:20 +0000 (UTC)
Date: Wed, 17 Aug 2016 11:31:20 +0000 (UTC)
From: "Prabhjyot Singh (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12997884.1471433429000.328471.1471433480508@Atlassian.JIRA>
In-Reply-To: <JIRA.12997884.1471433429000@Atlassian.JIRA>
References: <JIRA.12997884.1471433429000@Atlassian.JIRA> <JIRA.12997884.1471433429126@arcas>
Subject: [jira] [Created] (AMBARI-18182) Ambari server start fails (become
 stopped) after upgrade with java.lang.NoSuchFieldError: IS_SECURITY_ENABLED
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Wed, 17 Aug 2016 11:31:22 -0000

Prabhjyot Singh created AMBARI-18182:
----------------------------------------

             Summary: Ambari server start fails (become stopped) after upgrade with java.lang.NoSuchFieldError: IS_SECURITY_ENABLED
                 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)