Re: AW: embeded tomcat apache-jasper dependency
On 18/05/2022 20:24, Rob Sargent wrote: On 5/18/22 12:21, Rob Sargent wrote: On 5/17/22 01:24, Mark Thomas wrote: On 17/05/2022 08:13, Thomas Hoffmann (Speed4Trade GmbH) wrote: Hello, -Ursprüngliche Nachricht- Von: Rob Sargent Gesendet: Dienstag, 17. Mai 2022 00:38 An: users@tomcat.apache.org Betreff: embeded tomcat apache-jasper dependency I'm seeing a new-to-me deployment failure and am at a loss to explain. Using tomcat 9-0-63 (and getting Caused by: java.lang.IllegalArgumentException: More than one fragment with the name [org_apache_jasper_el] was found. This is not legal with relative ordering. See section 8.2.2 2c of the Servlet specification for details. Consider using absolute ordering. at Any pointers appreciated. rjs This message probably refers to web-fragments. They are usually located at: /META-INF/web-fragment.xml Within this XML there can be an ordering element an a name element . Maybe you can inspect the jars for this file. It looks like you are packaging at least one of the standard Tomcat JARs (either jasper-el.jar or tomcat-embed-el.jar) in your web application. That will trigger this error. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org Thank you. Deleting /everything/ and starting over from scratch should be my first instinct, rather than last... I do still get an exception at startup SEVERE: Servlet [jsp] in web application [/sgs] threw load() exception java.lang.ClassNotFoundException: org.apache.jasper.servlet.JspServlet at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1412) at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1220) at org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:534) at org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:515) at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:149) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1070) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1010) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4957) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5264) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1396) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1386) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:145) at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:919) at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:835) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1396) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1386) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:145) at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:919) at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:263) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.StandardService.startInternal(StandardService.java:432) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:927) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.startup.Tomcat.start(Tomcat.java:486) at edu.utah.camplab.server.SGSSelector.kickOff(SGSSelector.java:175) at edu.utah.camplab.server.SGSSelector.run(SGSSelector.java:187) at java.base/java.lang.Thread.run(Thread.java:833) so
Re: AW: embeded tomcat apache-jasper dependency
On 5/18/22 12:21, Rob Sargent wrote: On 5/17/22 01:24, Mark Thomas wrote: On 17/05/2022 08:13, Thomas Hoffmann (Speed4Trade GmbH) wrote: Hello, -Ursprüngliche Nachricht- Von: Rob Sargent Gesendet: Dienstag, 17. Mai 2022 00:38 An: users@tomcat.apache.org Betreff: embeded tomcat apache-jasper dependency I'm seeing a new-to-me deployment failure and am at a loss to explain. Using tomcat 9-0-63 (and getting Caused by: java.lang.IllegalArgumentException: More than one fragment with the name [org_apache_jasper_el] was found. This is not legal with relative ordering. See section 8.2.2 2c of the Servlet specification for details. Consider using absolute ordering. at Any pointers appreciated. rjs This message probably refers to web-fragments. They are usually located at: /META-INF/web-fragment.xml Within this XML there can be an ordering element an a name element . Maybe you can inspect the jars for this file. It looks like you are packaging at least one of the standard Tomcat JARs (either jasper-el.jar or tomcat-embed-el.jar) in your web application. That will trigger this error. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org Thank you. Deleting /everything/ and starting over from scratch should be my first instinct, rather than last... I do still get an exception at startup SEVERE: Servlet [jsp] in web application [/sgs] threw load() exception java.lang.ClassNotFoundException: org.apache.jasper.servlet.JspServlet at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1412) at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1220) at org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:534) at org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:515) at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:149) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1070) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1010) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4957) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5264) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1396) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1386) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:145) at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:919) at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:835) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1396) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1386) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:145) at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:919) at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:263) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.StandardService.startInternal(StandardService.java:432) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:927) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.startup.Tomcat.start(Tomcat.java:486) at edu.utah.camplab.server.SGSSelector.kickOff(SGSSelector.java:175) at edu.utah.camplab.server.SGSSelector.run(SGSSelector.java:187) at java.base/java.lang.Thread.run(Thread.java:833) so I'm not completely clear of the hurdle. But I'm not using JSPs so I'll leave this for now - but maybe that's why I had a jasper dependency.
Re: AW: embeded tomcat apache-jasper dependency
On 5/17/22 01:24, Mark Thomas wrote: On 17/05/2022 08:13, Thomas Hoffmann (Speed4Trade GmbH) wrote: Hello, -Ursprüngliche Nachricht- Von: Rob Sargent Gesendet: Dienstag, 17. Mai 2022 00:38 An: users@tomcat.apache.org Betreff: embeded tomcat apache-jasper dependency I'm seeing a new-to-me deployment failure and am at a loss to explain. Using tomcat 9-0-63 (and getting Caused by: java.lang.IllegalArgumentException: More than one fragment with the name [org_apache_jasper_el] was found. This is not legal with relative ordering. See section 8.2.2 2c of the Servlet specification for details. Consider using absolute ordering. at Any pointers appreciated. rjs This message probably refers to web-fragments. They are usually located at: /META-INF/web-fragment.xml Within this XML there can be an ordering element an a name element . Maybe you can inspect the jars for this file. It looks like you are packaging at least one of the standard Tomcat JARs (either jasper-el.jar or tomcat-embed-el.jar) in your web application. That will trigger this error. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org Thank you. Deleting /everything/ and starting over from scratch should be my first instinct, rather than last...
Re: AW: embeded tomcat apache-jasper dependency
On 17/05/2022 08:13, Thomas Hoffmann (Speed4Trade GmbH) wrote: Hello, -Ursprüngliche Nachricht- Von: Rob Sargent Gesendet: Dienstag, 17. Mai 2022 00:38 An: users@tomcat.apache.org Betreff: embeded tomcat apache-jasper dependency I'm seeing a new-to-me deployment failure and am at a loss to explain. Using tomcat 9-0-63 (and getting Caused by: java.lang.IllegalArgumentException: More than one fragment with the name [org_apache_jasper_el] was found. This is not legal with relative ordering. See section 8.2.2 2c of the Servlet specification for details. Consider using absolute ordering. at org.apache.tomcat.util.descriptor.web.WebXml.orderWebFragments(WebX ml.java:2262) at org.apache.tomcat.util.descriptor.web.WebXml.orderWebFragments(WebX ml.java:2220) My dependency manager (gradle) finds mention of jasper as an explicit dependency \--- project :webapp +--- project :transport (*) +--- com.fasterxml.jackson.core:jackson-databind:2.11.4 (*) +--- com.fasterxml.jackson.core:jackson-core:2.11.4 +--- com.fasterxml.jackson.core:jackson-annotations:2.11.4 +--- com.fasterxml.jackson.datatype:jackson-datatype-jsr310:2.11.4 (*) +--- javax.servlet:javax.servlet-api:3.1.0 +--- javax.servlet.jsp:javax.servlet.jsp-api:2.3.3 +--- org.apache.tomcat.embed:tomcat-embed-core:9.0.+ -> 9.0.63 | \--- org.apache.tomcat:tomcat-annotations-api:9.0.63 +--- org.apache.tomcat.embed:tomcat-embed-jasper:9.0.+ -> 9.0.63 | +--- org.apache.tomcat.embed:tomcat-embed-core:9.0.63 (*) | +--- org.apache.tomcat.embed:tomcat-embed-el:9.0.63 | \--- org.eclipse.jdt:ecj:3.18.0 +--- org.apache.tomcat.embed:tomcat-embed-logging-juli:9.0.0.M6 +--- org.apache.tomcat:tomcat-jdbc:9.0.+ -> 9.0.63 | \--- org.apache.tomcat:tomcat-juli:9.0.63 +--- org.apache.tomcat:tomcat-dbcp:9.0.+ -> 9.0.63 | \--- org.apache.tomcat:tomcat-juli:9.0.63 +--- org.apache.tomcat:tomcat-juli:9.0.+ -> 9.0.63 \--- org.slf4j:slf4j-api:1.7.7 -> 1.7.32 I see no evidence of even a single instance of the string "org_apache_jasper_el" (not even just "jasper") in any xml file in the deployment directory. Even if I remove the jasper dependency (I'm not using JSF) and rebuild (distTar) the project I get the same complaint (more than one jasper fragment). Any pointers appreciated. rjs This message probably refers to web-fragments. They are usually located at: /META-INF/web-fragment.xml Within this XML there can be an ordering element an a name element . Maybe you can inspect the jars for this file. It looks like you are packaging at least one of the standard Tomcat JARs (either jasper-el.jar or tomcat-embed-el.jar) in your web application. That will trigger this error. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
AW: embeded tomcat apache-jasper dependency
Hello, > -Ursprüngliche Nachricht- > Von: Rob Sargent > Gesendet: Dienstag, 17. Mai 2022 00:38 > An: users@tomcat.apache.org > Betreff: embeded tomcat apache-jasper dependency > > I'm seeing a new-to-me deployment failure and am at a loss to explain. > > > Using tomcat 9-0-63 (and getting > > Caused by: java.lang.IllegalArgumentException: More than one > fragment with the name [org_apache_jasper_el] was found. This is not > legal with relative ordering. See section 8.2.2 2c of the Servlet > specification for details. Consider using absolute ordering. > at > > org.apache.tomcat.util.descriptor.web.WebXml.orderWebFragments(WebX > ml.java:2262) > at > > org.apache.tomcat.util.descriptor.web.WebXml.orderWebFragments(WebX > ml.java:2220) > > > My dependency manager (gradle) finds mention of jasper as an explicit > dependency > > \--- project :webapp > +--- project :transport (*) > +--- com.fasterxml.jackson.core:jackson-databind:2.11.4 (*) > +--- com.fasterxml.jackson.core:jackson-core:2.11.4 > +--- com.fasterxml.jackson.core:jackson-annotations:2.11.4 > +--- > com.fasterxml.jackson.datatype:jackson-datatype-jsr310:2.11.4 (*) > +--- javax.servlet:javax.servlet-api:3.1.0 > +--- javax.servlet.jsp:javax.servlet.jsp-api:2.3.3 > +--- org.apache.tomcat.embed:tomcat-embed-core:9.0.+ -> > 9.0.63 > | \--- org.apache.tomcat:tomcat-annotations-api:9.0.63 > +--- org.apache.tomcat.embed:tomcat-embed-jasper:9.0.+ -> > 9.0.63 > | +--- > org.apache.tomcat.embed:tomcat-embed-core:9.0.63 (*) > | +--- org.apache.tomcat.embed:tomcat-embed-el:9.0.63 > | \--- org.eclipse.jdt:ecj:3.18.0 > +--- > org.apache.tomcat.embed:tomcat-embed-logging-juli:9.0.0.M6 > +--- org.apache.tomcat:tomcat-jdbc:9.0.+ -> 9.0.63 > | \--- org.apache.tomcat:tomcat-juli:9.0.63 > +--- org.apache.tomcat:tomcat-dbcp:9.0.+ -> 9.0.63 > | \--- org.apache.tomcat:tomcat-juli:9.0.63 > +--- org.apache.tomcat:tomcat-juli:9.0.+ -> 9.0.63 > \--- org.slf4j:slf4j-api:1.7.7 -> 1.7.32 > > I see no evidence of even a single instance of the string > "org_apache_jasper_el" (not even just "jasper") in any xml file in the > deployment directory. > > Even if I remove the jasper dependency (I'm not using JSF) and rebuild > (distTar) the project I get the same complaint (more than one jasper > fragment). > > > > Any pointers appreciated. > rjs This message probably refers to web-fragments. They are usually located at: /META-INF/web-fragment.xml Within this XML there can be an ordering element an a name element . Maybe you can inspect the jars for this file. Greetings, Thomas
