Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    Expert tip

    jsp-api and servlet-api jars must NOT be deployed by your web app. They should be marked as provided but not deployed by your app.

  2. ,
    Expert tip

    The server rejects all jars that already belong to the server runtime (such as tomcat-**.jar, servlet**.jar). Consider substituting the CORS filter you're using for this one:

Solutions on the web

via GitHub by gregw
, 1 year ago
java.lang.ClassNotFoundException:	at	at org.eclipse.jetty.webapp.WebAppClassLoader.findClass(	at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(	at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(	at	at org.eclipse.jetty.webapp.WebAppContext.configure(	at org.eclipse.jetty.webapp.WebAppContext.startContext(	at org.eclipse.jetty.server.handler.ContextHandler.doStart(	at org.eclipse.jetty.servlet.ServletContextHandler.doStart(	at org.eclipse.jetty.webapp.WebAppContext.doStart(	at	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(	at	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(	at org.eclipse.jetty.util.component.ContainerLifeCycle.start(	at org.eclipse.jetty.server.Server.start(	at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(	at org.eclipse.jetty.server.handler.AbstractHandler.doStart(	at org.eclipse.jetty.server.Server.doStart(	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(	at org.eclipse.jetty.xml.XmlConfiguration$	at Method)	at org.eclipse.jetty.xml.XmlConfiguration.main(