[ 
https://issues.apache.org/jira/browse/AMBARI-26297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17931867#comment-17931867
 ] 

Bhavik Patel commented on AMBARI-26297:
---------------------------------------

[~jialiang]  Is this Jira filed to resolve the below error:


{code:java}
ambari-server/resources/views/work/ADMIN_VIEW{2.7.9}}
javax.naming.NoInitialContextException: Cannot instantiate class: 
org.eclipse.jetty.jndi.InitialContextFactory [Root exception is 
java.lang.ClassNotFoundException: org.eclipse.jetty.jndi.InitialContextFactory]
        at 
java.naming/javax.naming.spi.NamingManager.getFactory(NamingManager.java:762)
        at 
java.naming/javax.naming.spi.NamingManager.lambda$getInitialContext$1(NamingManager.java:724)
        at 
java.base/jdk.internal.loader.AbstractClassLoaderValue$Memoizer.get(AbstractClassLoaderValue.java:329)
        at 
java.base/jdk.internal.loader.AbstractClassLoaderValue.computeIfAbsent(AbstractClassLoaderValue.java:205)
        at 
java.naming/javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:724)
        at 
java.naming/javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:305)
        at java.naming/javax.naming.InitialContext.init(InitialContext.java:236)
        at 
java.naming/javax.naming.InitialContext.<init>(InitialContext.java:184)
        at 
org.eclipse.jetty.plus.webapp.EnvConfiguration.createEnvContext(EnvConfiguration.java:264)
        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)
        at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:93)
        at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:171)
        at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:121)
        at 
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:89)
        at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:93)
        at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:171)
        at org.eclipse.jetty.server.Server.start(Server.java:470)
        at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
        at 
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:89)
        at org.eclipse.jetty.server.Server.doStart(Server.java:415)
        at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:93)
        at 
org.apache.ambari.server.controller.AmbariServer.run(AmbariServer.java:567)
        at 
org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:1118)
Caused by: java.lang.ClassNotFoundException: 
org.eclipse.jetty.jndi.InitialContextFactory
        at 
org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:531)
        at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525)
        at java.base/java.lang.Class.forName0(Native Method)
        at java.base/java.lang.Class.forName(Class.java:467)
        at 
java.naming/com.sun.naming.internal.VersionHelper.loadClass(VersionHelper.java:128)
        at 
java.naming/com.sun.naming.internal.VersionHelper.loadClass(VersionHelper.java:134)
        at 
java.naming/com.sun.naming.internal.VersionHelper.loadClass(VersionHelper.java:97)
        at 
java.naming/javax.naming.spi.NamingManager.getFactory(NamingManager.java:759)
        ... 25 more




INFO [main] StompEventsMetricsSource:61 - Starting stomp events source...
WARN [qtp-ambari-agent-56] HttpChannel:802 - handleException /ca 
org.eclipse.jetty.http.BadMessageException: 400: Invalid SNI
WARN [qtp-ambari-agent-56] HttpChannel:802 - handleException /ca 
org.eclipse.jetty.http.BadMessageException: 400: Invalid SNI {code}

> Fix WebSocket compatibility issues after Spring upgrade
> -------------------------------------------------------
>
>                 Key: AMBARI-26297
>                 URL: https://issues.apache.org/jira/browse/AMBARI-26297
>             Project: Ambari
>          Issue Type: Technical task
>            Reporter: Jialiang Cai
>            Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to