You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Bhavik Patel (Jira)" <ji...@apache.org> on 2025/04/16 06:33:00 UTC
[jira] [Comment Edited] (AMBARI-26438) Ambari capacity view add failed
[ https://issues.apache.org/jira/browse/AMBARI-26438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17944945#comment-17944945 ]
Bhavik Patel edited comment on AMBARI-26438 at 4/16/25 6:32 AM:
----------------------------------------------------------------
Can you please create multiple instance of capacity scheduler and validate?
Im observing below error
{code:java}
WARN [ambari-client-thread-58] WebAppContext:512 - Failed startup of context oeje10w.WebAppContext@5d510ffc{/views/CAPACITY-SCHEDULER/1.0.0/cp7,/views/CAPACITY-SCHEDULER/1.0.0/cp7,b=file:///var/lib/ambari-server/resources/views/work/CAPACITY-SCHEDULER%7B1.0.0%7D/,a=STOPPED,h=oaasc.AmbariHandlerList$SharedSessionHandler@757093bf{STOPPED}}{/var/lib/ambari-server/resources/views/work/CAPACITY-SCHEDULER{1.0.0}}
java.lang.RuntimeException: javax.naming.NamingException: This context is immutable; remaining name 'env'
at org.eclipse.jetty.ee10.plus.webapp.EnvConfiguration.createEnvContext(EnvConfiguration.java:239)
at org.eclipse.jetty.ee10.plus.webapp.EnvConfiguration.preConfigure(EnvConfiguration.java:66)
at org.eclipse.jetty.ee10.webapp.Configurations.preConfigure(Configurations.java:487)
at org.eclipse.jetty.ee10.webapp.WebAppContext.preConfigure(WebAppContext.java:461)
at org.eclipse.jetty.ee10.webapp.WebAppContext.doStart(WebAppContext.java:502)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:93)
at org.apache.ambari.server.controller.AmbariHandlerList.addViewInstance(AmbariHandlerList.java:188)
at org.apache.ambari.server.view.ViewRegistry.installViewInstance(ViewRegistry.java:606) {code}
was (Author: bpatel):
Can you please create multiple instance of capacity scheduler and validate?
> 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: issues-unsubscribe@ambari.apache.org
For additional commands, e-mail: issues-help@ambari.apache.org