You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Martin Schreier (Jira)" <ji...@apache.org> on 2022/04/15 21:48:00 UTC

[jira] [Commented] (MRM-2046) After upgrade war file from 2.2.5 to 2.2.6 a ClassNotFoundException is thrown org.eclipse.jetty.servlet.DefaultServlet

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

Martin Schreier commented on MRM-2046:
--------------------------------------

Yes, this was a regression from this release. The current snapshot version 2.2.8-SNAPSHOT should not have this problem.
As workaround you can remove this entry from the web.xml:

 
{code:java}
<!-- Removing dir-listing from Jetty default-servlet -->
  <servlet>
    <servlet-name>default</servlet-name>
    <servlet-class>org.eclipse.jetty.servlet.DefaultServlet</servlet-class>
    <init-param>
      <param-name>dirAllowed</param-name>
      <param-value>false</param-value>
    </init-param>
    <load-on-startup>0</load-on-startup>
  </servlet>{code}

> After upgrade war file from 2.2.5 to 2.2.6 a ClassNotFoundException is thrown  org.eclipse.jetty.servlet.DefaultServlet
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: MRM-2046
>                 URL: https://issues.apache.org/jira/browse/MRM-2046
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 2.2.6
>         Environment: Tomcat 8.5.49
>            Reporter: Thomas Hoffmann
>            Priority: Major
>
> I am using the war deployment of archiva on Tomcat 8.5.
> When upgrading from 2.2.5 to 2.2.6 something changed in the dependencies.
> I get the following error / stack:
> {noformat}
> 15-Apr-2022 22:38:56.963 SCHWERWIEGEND [repo-startStop-1] org.apache.catalina.core.StandardContext.loadOnStartup Servlet [default] in web application [/archiva] threw load() exception
>     java.lang.ClassNotFoundException: org.eclipse.jetty.servlet.DefaultServlet
>         at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1358)
>         at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1180)
>         at org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:546)
>         at org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:527)
>         at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:150)
>         at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1044)
>         at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:985)
>         at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4885)
>         at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5199)
>         at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
>         at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:743)
>         at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:719)
>         at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:705)
>         at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:614)
>         at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1823)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
>         at java.util.concurrent.FutureTask.run(Unknown Source)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>         at java.lang.Thread.run(Unknown Source){noformat}
>  
> It seems new dependencies were introduced (?)
> As the servlet can't get loaded, the website of archiva is not available .
> Switching back to 2.2.5, everything works fine again.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)