Re: embeded tomcat apache-jasper dependency

2022-08-15 Thread Rob Sargent



On 8/15/22 19:55, Shakila Rajaiah wrote:

Earlier Noelette replied:
It looks like you have multiple locations/instances of the same jar 
file (jasper-el.jar by the looks of the error message). This is 
typically included with tomcat. Are you also including a version with 
your application?


I think that I accidently did. Please look at the steps I tried. I am 
unable to remove these .jar files from Eclipse. Therefore I keep 
getting the error. Any help will do





Hello Mark Thomas, Noelette Stout, & Tomcat Users,


I am trying to deploy two war files to Tomcat server. The first 
application deploys fine. The second application is erroring out and 
this is the error I am getting:



11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Server version 
name:   Apache Tomcat/9.0.46
11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Server built:   
  May 8 2021 17:35:52 UTC
11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Server version 
number: 9.0.46.0
11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log OS Name:     
 Windows Server 2012 R2
11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log OS Version:     6.3
11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Architecture:   
  amd64
11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Java Home:     
 C:\Program Files\Java\jre1.8.0_291
11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log JVM Version:     
 1.8.0_291-b10
11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor:     
Oracle Corporation
11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:   
   C:\apache-tomcat-9.0.46
11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:   
   C:\apache-tomcat-9.0.46
11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: 
-Djava.util.logging.config.file=C:\apache-tomcat-9.0.46\conf\logging.properties
11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: 
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: -Djdk.tls.ephemeralDHKeySize=2048
11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: -Dignore.endorsed.dirs=
11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: -Dcatalina.base=C:\apache-tomcat-9.0.46
11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: -Dcatalina.home=C:\apache-tomcat-9.0.46
11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: -Djava.io.tmpdir=C:\apache-tomcat-9.0.46\temp
11-Aug-2022 10:04:21.414 INFO [main] 
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The 
Apache Tomcat Native library which allows using OpenSSL was not found 
on the java.library.path: [C:\Program 
Files\Java\jre1.8.0_291\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Prog
ram Files (x86)\Common 
Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\apache-maven-3.8.1\bin;C:\Program 
Files\Java\jre1.8.0_291\bin;C:\Program 
Files\Java\jre1.8.0_291;C:\apache-tomcat-9.0.45;C:\apache-tomcat-9.0.45\bi
n;C:\Program Files\Java\jdk1.8.0_291\bin;C:\Program Files 
(x86)\Microsoft SQL Server\150\DTS\Binn\;C:\Program Files\Azure Data 
Studio\bin;.]
11-Aug-2022 10:04:21.862 INFO [main] 
org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler 
["http-nio-8080"]
11-Aug-2022 10:04:21.971 INFO [main] 
org.apache.catalina.startup.Catalina.load Server initialization in 
[842] milliseconds
11-Aug-2022 10:04:22.002 INFO [main] 
org.apache.catalina.core.StandardService.startInternal Starting 
service [Catalina]
11-Aug-2022 10:04:22.002 INFO [main] 
org.apache.catalina.core.StandardEngine.startInternal Starting Servlet 
engine: [Apache Tomcat/9.0.46]
11-Aug-2022 10:04:22.033 INFO [main] 
org.apache.catalina.startup.HostConfig.deployWAR Deploying web 
application archive [C:\apache-tomcat-9.0.46\webapps\ROOT.war]
11-Aug-2022 10:04:25.971 SEVERE [main] 
org.apache.catalina.startup.HostConfig.deployWAR Error deploying web 
application 

embeded tomcat apache-jasper dependency

2022-08-15 Thread Shakila Rajaiah
Earlier Noelette replied:It looks like you have multiple locations/instances of 
the same jar file (jasper-el.jar by the looks of the error message). This is 
typically included with tomcat. Are you also including a version with your 
application?

I think that I accidently did. Please look at the steps I tried. I am unable to 
remove these .jar files from Eclipse. Therefore I keep getting the error. Any 
help will do 



Hello Mark Thomas, Noelette Stout, & Tomcat Users,

I am trying to deploy two war files to Tomcat server. The first application 
deploys fine. The second application is erroring out and this is the error I am 
getting:

11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Server version name:   
Apache Tomcat/9.0.4611-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Server built:          
May 8 2021 17:35:52 UTC11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Server version number: 
9.0.46.011-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log OS Name:               
Windows Server 2012 R211-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log OS Version:            
6.311-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Architecture:          
amd6411-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Java Home:             
C:\Program Files\Java\jre1.8.0_29111-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log JVM Version:           
1.8.0_291-b1011-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor:            
Oracle Corporation11-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:         
C:\apache-tomcat-9.0.4611-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:         
C:\apache-tomcat-9.0.4611-Aug-2022 10:04:21.393 INFO [main] 
org.apache.catalina.startup.VersionLoggerListener.log Command line argument: 
-Djava.util.logging.config.file=C:\apache-tomcat-9.0.46\conf\logging.properties11-Aug-2022
 10:04:21.393 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log 
Command line argument: 
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager11-Aug-2022 
10:04:21.393 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log 
Command line argument: -Djdk.tls.ephemeralDHKeySize=204811-Aug-2022 
10:04:21.393 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log 
Command line argument: 
-Djava.protocol.handler.pkgs=org.apache.catalina.webresources11-Aug-2022 
10:04:21.393 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log 
Command line argument: -Dignore.endorsed.dirs=11-Aug-2022 10:04:21.393 INFO 
[main] org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: -Dcatalina.base=C:\apache-tomcat-9.0.4611-Aug-2022 10:04:21.393 INFO 
[main] org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: -Dcatalina.home=C:\apache-tomcat-9.0.4611-Aug-2022 10:04:21.393 INFO 
[main] org.apache.catalina.startup.VersionLoggerListener.log Command line 
argument: -Djava.io.tmpdir=C:\apache-tomcat-9.0.46\temp11-Aug-2022 10:04:21.414 
INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The 
Apache Tomcat Native library which allows using OpenSSL was not found on the 
java.library.path: [C:\Program 
Files\Java\jre1.8.0_291\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program
 Files (x86)\Common 
Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\apache-maven-3.8.1\bin;C:\Program
 Files\Java\jre1.8.0_291\bin;C:\Program 
Files\Java\jre1.8.0_291;C:\apache-tomcat-9.0.45;C:\apache-tomcat-9.0.45\bin;C:\Program
 Files\Java\jdk1.8.0_291\bin;C:\Program Files (x86)\Microsoft SQL 
Server\150\DTS\Binn\;C:\Program Files\Azure Data Studio\bin;.]11-Aug-2022 
10:04:21.862 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing 
ProtocolHandler ["http-nio-8080"]11-Aug-2022 10:04:21.971 INFO [main] 
org.apache.catalina.startup.Catalina.load Server initialization in [842] 
milliseconds11-Aug-2022 10:04:22.002 INFO [main] 
org.apache.catalina.core.StandardService.startInternal Starting service 
[Catalina]11-Aug-2022 10:04:22.002 INFO [main] 
org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: 
[Apache Tomcat/9.0.46]11-Aug-2022 10:04:22.033 INFO [main] 
org.apache.catalina.startup.HostConfig.deployWAR Deploying web application 
archive [C:\apache-tomcat-9.0.46\webapps\ROOT.war]11-Aug-2022 10:04:25.971 
SEVERE [main] org.apache.catalina.startup.HostConfig.deployWAR Error deploying 
web application archive 

Re: AW: embeded tomcat apache-jasper dependency

2022-05-19 Thread Mark Thomas

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

Re: AW: embeded tomcat apache-jasper dependency

2022-05-18 Thread Rob Sargent



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

2022-05-18 Thread Rob Sargent



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

2022-05-17 Thread Mark Thomas

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

2022-05-17 Thread Thomas Hoffmann (Speed4Trade GmbH)
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


embeded tomcat apache-jasper dependency

2022-05-16 Thread Rob Sargent

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(WebXml.java:2262)
    at
   
org.apache.tomcat.util.descriptor.web.WebXml.orderWebFragments(WebXml.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