[
https://issues.apache.org/jira/browse/AMBARI-26438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17946597#comment-17946597
]
Bhavik Patel commented on AMBARI-26438:
---------------------------------------
I tried the same steps but after removing jetty-plus jar from the
"/usr/lib/ambari-server directory" again the AMBARI-ADMIN view is not loading
and it throw the below error.
{code:java}
Caused by: java.lang.NoClassDefFoundError:
org/eclipse/jetty/plus/jndi/NamingEntry
at java.base/java.lang.Class.getDeclaredConstructors0(Native Method)
at
java.base/java.lang.Class.privateGetDeclaredConstructors(Class.java:3373)
at java.base/java.lang.Class.getConstructor0(Class.java:3578)
at java.base/java.lang.Class.getConstructor(Class.java:2271)
at java.base/java.util.ServiceLoader$1.run(ServiceLoader.java:666)
at java.base/java.util.ServiceLoader$1.run(ServiceLoader.java:663)
at
java.base/java.security.AccessController.doPrivileged(AccessController.java:569)
at
java.base/java.util.ServiceLoader.getConstructor(ServiceLoader.java:674)
... 23 more
Caused by: java.lang.ClassNotFoundException:
org.eclipse.jetty.plus.jndi.NamingEntry
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525)
... 31 more {code}
> Ambari capacity view add failed
> -------------------------------
>
> Key: AMBARI-26438
> URL: https://issues.apache.org/jira/browse/AMBARI-26438
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 3.1.0
> Reporter: Jialiang Cai
> Assignee: Jialiang Cai
> Priority: Major
> Fix For: 3.1.0
>
> Attachments: image-2025-04-12-09-55-02-642.png,
> image-2025-04-12-09-55-19-765.png, image-2025-04-12-09-55-43-697.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> !image-2025-04-12-09-55-43-697.png!!image-2025-04-12-09-55-02-642.png!
> 2025-04-08 18:43:15,308 WARN [ambari-client-thread-3677] WebAppContext:542 -
> Failed startup of context
> o.e.j.w.WebAppContext@7d565fbb\{/views/CAPACITY-SCHEDULER/1.0.0/view1,file:///var/lib/ambari-server/resources/views/work/CAPACITY-SCHEDULER%7B1.0.0%7D/,STOPPED}{/var/lib/ambari-server/resources/views/work/CAPACITY-SCHEDULER\{1.0.0}}
> javax.naming.NameAlreadyBoundException: env
> at
> org.eclipse.jetty.jndi.NamingContext.createSubcontext(NamingContext.java:372)
> at
> org.eclipse.jetty.jndi.NamingContext.createSubcontext(NamingContext.java:393)
> at
> org.eclipse.jetty.plus.webapp.EnvConfiguration.createEnvContext(EnvConfiguration.java:266)
> at
> org.eclipse.jetty.plus.webapp.EnvConfiguration.preConfigure(EnvConfiguration.java:78)
> at
> org.eclipse.jetty.webapp.Configurations.preConfigure(Configurations.java:496)
> at
> org.eclipse.jetty.webapp.WebAppContext.preConfigure(WebAppContext.java:510)
> at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:532)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
