AW: sslHostConfig and ciphers

2023-03-03 Thread Thomas Hoffmann (Speed4Trade GmbH) 
Hello,

this message originates from your used java. It's not from tomcat.
Java doesn't know this cipher-suite or is disabled in java.security

You can list the supported ciphers via some code lines like 
https://stackoverflow.com/questions/9333504/how-can-i-list-the-available-cipher-algorithms
  

Greetings, Thomas

> -Ursprüngliche Nachricht-
> Von: jonmcalexan...@wellsfargo.com.INVALID
> 
> Gesendet: Freitag, 3. März 2023 18:38
> An: users@tomcat.apache.org
> Betreff: sslHostConfig and ciphers
> 
> Ok, I don't know if I'm doing something wrong, or if I'm just not reading the
> output correctly.
> 
> I have JSSE connector using sslHostConfig and in there I have defined ciphers,
> as below:
> 
>  protocol="org.apache.coyote.http11.Http11NioProtocol"
> maxThreads="150"
> maxHttpHeaderSize="16384"
> compression="on"
> scheme="https"
> SSLEnabled="true"
> secure="true"
> defaultSSLHostConfigName="test.test">
>  hostName="test.test"
> protocols="TLSv1.2"
> ciphers="TLS_DHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH
> _AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
> TLS_DHE_DSS_WITH_AES_256_GCM_SHA384,TLS_DHE_RSA_WITH_AES_256_C
> CM,TLS_ECDHE_ECDSA_WITH_AES_256_CCM,TLS_DHE_RSA_WITH_AES_256_
> CCM_8,
> TLS_ECDHE_ECDSA_WITH_AES_256_CCM_8,TLS_DHE_RSA_WITH_AES_128_G
> CM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
> TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_DHE_DSS_WITH_AES_1
> 28_GCM_SHA256,TLS_DHE_RSA_WITH_AES_128_CCM,
> TLS_ECDHE_ECDSA_WITH_AES_128_CCM,TLS_DHE_RSA_WITH_AES_128_CCM
> _8,TLS_ECDHE_ECDSA_WITH_AES_128_CCM_8,
> TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_RSA_WITH_
> CHACHA20_POLY1305_SHA256,
> TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256"
>  certificateKeystoreFile=""
> certificateKeystorePassword ="${keystore.pass}"
> certificateKeyPassword="${keystore.pass}"
> certificateKeyAlias=""
> />
> 
> 
> 
> However, if I enable ssl debugging, I am getting the following messages in my
> catalina.out file.
> 
> 03-Mar-2023 16:43:22.120 INFO [main] org.apache.coyote.AbstractProtocol.init
> Initializing ProtocolHandler ["https-jsse-nio-9443"]
> javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.146
> UTC|SSLContextImpl.java:425|System property jdk.tls.client.cipherSuites is set
> to 'null'
> javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.150
> UTC|SSLContextImpl.java:425|System property jdk.tls.server.cipherSuites is set
> to 'null'
> javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.161
> UTC|SSLCipher.java:438|jdk.tls.keyLimits:  entry = AES/GCM/NoPadding
> KeyUpdate 2^37. AES/GCM/NOPADDING:KEYUPDATE = 137438953472
> javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.201
> UTC|SSLContextImpl.java:399|Ignore disabled cipher suite:
> TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA
> javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.201
> UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite:
> TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA
> javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.202
> UTC|SSLContextImpl.java:399|Ignore disabled cipher suite:
> TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
> javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.202
> UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite:
> TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
> javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.202
> UTC|SSLContextImpl.java:399|Ignore disabled cipher suite:
> SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA
> javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.202
> UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite:
> SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA
> javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.203
> UTC|SSLContextImpl.java:399|Ignore disabled cipher suite:
> SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA
> javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.212
> UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite:
> SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA
> javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.212
> UTC|SSLContextImpl.java:399|Ignore disabled cipher suite:
> TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA
> javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.213
> UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite:
> TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA
> javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.213
> UTC|SSLContextImpl.java:399|Ignore disabled cipher suite:
> TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA
> javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.213
> UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite:
> TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA
> javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.213
> UTC|SSLContextImpl.java:399|Ignore disabled cipher suite:
> SSL_RSA_WITH_3DES_EDE_CBC_SHA
> javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.214
> UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite:
> SSL_RSA_WITH_3DES_EDE_CBC_SHA
> javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.221
> UTC|SSLContextImpl.java:399|Ignore disabled cipher suite:
> TLS_DH_anon_WITH_AES_256_GCM_SHA384
> javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.221
> UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite:
> TLS_DH_anon_WITH_AES_256_GCM

9.0.73 change log

2023-03-03 Thread Adam Rauch 

Thanks, Tomcat team, for cranking out another release!

I noticed a minor discrepancy on the main website home page 
(https://tomcat.apache.org/). In the "Tomcat 9.0.73 Released" section, 
"Tomcat 9 changelog" links to the 9.0.71 bookmark 
("#Tomcat_9.0.71_(remm)") instead of the 9.0.73 bookmark.


Thanks,
Adam


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Tomcat 9.0.71 Anomalies

2023-03-03 Thread jonmcalexander 
Hi Mark,

On the slowness, this is when they are retrieving random .js files from the 
exploded war file after deployment. It's taking an a long
 amount of time. Some of these are quite large, like 2MB or more. When the 
issue shows, doing a curl we get to here and then it pauses for some time 
before it feeds back the data.

*   Trying **.**.**.**:8443...
* TCP_NODELAY set
* Connected to server port 8443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / 
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: 
*  start date: 
*  expire date: 
*  issuer: 
*  SSL certificate verify result: unable to get local issuer certificate (20), 
continuing anyway.
> GET  HTTP/1.1
> Host: 
> User-Agent: curl/7.65.3
> Accept: */*
>

And it just hangs out here before finally getting the requested file.

In looking at the catalina.out log file, I am not seeing any 
errors/stack-traces.

Any ideas as to what may be causing this?

Thank you,

Dream * Excel * Explore * Inspire
Jon McAlexander
Senior Infrastructure Engineer
Asst. Vice President
He/His

Middleware Product Engineering
Enterprise CIO | EAS | Middleware | Infrastructure Solutions

8080 Cobblestone Rd | Urbandale, IA 50322
MAC: F4469-010
Tel 515-988-2508 | Cell 515-988-2508

jonmcalexan...@wellsfargo.com
This message may contain confidential and/or privileged information. If you are 
not the addressee or authorized to receive this for the addressee, you must not 
use, copy, disclose, or take any action based on this message or any 
information herein. If you have received this message in error, please advise 
the sender immediately by reply e-mail and delete this message. Thank you for 
your cooperation.

> -Original Message-
> From: Mark Thomas 
> Sent: Friday, March 3, 2023 1:32 AM
> To: users@tomcat.apache.org
> Subject: Re: Tomcat 9.0.71 Anomalies
> 
> On 02/03/2023 21:54, jonmcalexan...@wellsfargo.com.INVALID wrote:
> > Hello gentle beings,
> >
> > I have a couple of application teams having issues since getting upgraded to
> Tomcat 9.0.71.
> 
> Upgrading from which Tomcat version?
> 
> > The main one has to do with an application that has run fine in the past is
> now exceeding max cursors with their Oracle Database datasource. They are
> using spring framework to control the Database operations. Here is what
> their resource looks like:
> >
> >  type="javax.sql.DataSource"
> > maxTotal="100" maxIdle="30" maxWaitMillis="15000"
> > username="${datasource.fm.username}"
> password="${datasource.fm.password}"
> driverClassName="oracle.jdbc.OracleDriver"
> >
> url="jdbc:oracle:thin:@(Description=(CONNECT_TIMEOUT=10)(RETRY_COUN
> T=3)(ADDRESS_LIST=(LOAD_BALANCE=on)(FAILOVER=ON)(ADDRESS=(PROT
> OCOL=tcp)(HOST=***)(PORT=3203))(ADDRESS=(PROTOCOL=
> tcp)(HOST=*)(PORT=3203)))(CONNECT_DATA=(SERVICE
> _NAME=ceofm_u)))"/>
> >
> > Here is an error from the log file:
> >
> > [‎3/‎2/‎2023 1:50 PM]  Burgos, Maria D.:
> > here is the error in catalina.out
> > 02-Mar-2023 13:05:30.944 SEVERE [https-jsse-nio-28443-exec-8]
> org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for
> servlet [f***servlet] in context with path [/f***] threw exception [Request
> processing failed; nested exception is
> com.wellsfargo.fms.common.exception.FMSException] with root cause
> >  com.wellsfargo.f**.common.exception.F**Exception
> >  at
> org.springframework.jdbc.core.JdbcTemplate.translateException(JdbcTempl
> ate.java:1542)
> >  at
> org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:66
> 7)
> 
> Any chance we can see a root cause for that? Something from the JDBC
> driver?
> 
> > The other team is having performance issues when using static .jar
> resources in their war file. One part of the app, on the browser side
> measurements, is taking 2.2 minutes to load. This started getting worse after
> moving to 9.0.71. Are there any known issues that could be causing this?
> Currently waiting for 9.0.73 to get release. :)
> 
> Do you mean static resources stored in a JAR's META-INF/resources
> directory?
> 
> Is the WAR deployed in packed or unpacked form?
> 
> Mark
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Connector definitions, Re: Tomcat 8 impending EOL -- what's the minimum Java for Tomcat 9?

2023-03-03 Thread James H. H. Lampert 

On 3/3/23 9:51 AM, Mark Thomas wrote:

Yes.


Thanks. That simplifies things.

--
JHHL

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Connector definitions, Re: Tomcat 8 impending EOL -- what's the minimum Java for Tomcat 9?

2023-03-03 Thread Mark Thomas 

On 03/03/2023 17:44, James H. H. Lampert wrote:

On 3/2/23 3:50 PM, jonmcalexan...@wellsfargo.com.INVALID wrote:

Yes, Tomcat9 runs under Java8 and above.


Ok, another question: will Tomcat 9 accept a "legacy" connector 
definition in the form as shown below?


  protocol="org.apache.coyote.http11.Http11Protocol" maxThreads="150" 
SSLEnabled="true" scheme="https" secure="true" 
keystoreFile="/foo/tomcat/bar.ks" keyAlias="baz" clientAuth="false" 
sslProtocol="TLS" />


Yes.

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Connector definitions, Re: Tomcat 8 impending EOL -- what's the minimum Java for Tomcat 9?

2023-03-03 Thread James H. H. Lampert 

On 3/2/23 3:50 PM, jonmcalexan...@wellsfargo.com.INVALID wrote:

Yes, Tomcat9 runs under Java8 and above.


Ok, another question: will Tomcat 9 accept a "legacy" connector 
definition in the form as shown below?


 protocol="org.apache.coyote.http11.Http11Protocol" maxThreads="150" 
SSLEnabled="true" scheme="https" secure="true" 
keystoreFile="/foo/tomcat/bar.ks" keyAlias="baz" clientAuth="false" 
sslProtocol="TLS" />


--
JHHL

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

sslHostConfig and ciphers

2023-03-03 Thread jonmcalexander 
Ok, I don't know if I'm doing something wrong, or if I'm just not reading the 
output correctly.

I have JSSE connector using sslHostConfig and in there I have defined ciphers, 
as below:






However, if I enable ssl debugging, I am getting the following messages in my 
catalina.out file.

03-Mar-2023 16:43:22.120 INFO [main] org.apache.coyote.AbstractProtocol.init 
Initializing ProtocolHandler ["https-jsse-nio-9443"]
javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.146 
UTC|SSLContextImpl.java:425|System property jdk.tls.client.cipherSuites is set 
to 'null'
javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.150 
UTC|SSLContextImpl.java:425|System property jdk.tls.server.cipherSuites is set 
to 'null'
javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.161 
UTC|SSLCipher.java:438|jdk.tls.keyLimits:  entry = AES/GCM/NoPadding KeyUpdate 
2^37. AES/GCM/NOPADDING:KEYUPDATE = 137438953472
javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.201 
UTC|SSLContextImpl.java:399|Ignore disabled cipher suite: 
TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA
javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.201 
UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite: 
TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA
javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.202 
UTC|SSLContextImpl.java:399|Ignore disabled cipher suite: 
TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.202 
UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite: 
TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.202 
UTC|SSLContextImpl.java:399|Ignore disabled cipher suite: 
SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA
javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.202 
UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite: 
SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA
javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.203 
UTC|SSLContextImpl.java:399|Ignore disabled cipher suite: 
SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA
javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.212 
UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite: 
SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA
javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.212 
UTC|SSLContextImpl.java:399|Ignore disabled cipher suite: 
TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA
javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.213 
UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite: 
TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA
javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.213 
UTC|SSLContextImpl.java:399|Ignore disabled cipher suite: 
TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA
javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.213 
UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite: 
TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA
javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.213 
UTC|SSLContextImpl.java:399|Ignore disabled cipher suite: 
SSL_RSA_WITH_3DES_EDE_CBC_SHA
javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.214 
UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite: 
SSL_RSA_WITH_3DES_EDE_CBC_SHA
javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.221 
UTC|SSLContextImpl.java:399|Ignore disabled cipher suite: 
TLS_DH_anon_WITH_AES_256_GCM_SHA384
javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.221 
UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite: 
TLS_DH_anon_WITH_AES_256_GCM_SHA384
javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.221 
UTC|SSLContextImpl.java:399|Ignore disabled cipher suite: 
TLS_DH_anon_WITH_AES_128_GCM_SHA256
javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.222 
UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite: 
TLS_DH_anon_WITH_AES_128_GCM_SHA256
javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.222 
UTC|SSLContextImpl.java:399|Ignore disabled cipher suite: 
TLS_DH_anon_WITH_AES_256_CBC_SHA256
javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.222 
UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite: 
TLS_DH_anon_WITH_AES_256_CBC_SHA256
javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.222 
UTC|SSLContextImpl.java:399|Ignore disabled cipher suite: 
TLS_ECDH_anon_WITH_AES_256_CBC_SHA
javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.223 
UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite: 
TLS_ECDH_anon_WITH_AES_256_CBC_SHA
javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.223 
UTC|SSLContextImpl.java:399|Ignore disabled cipher suite: 
TLS_DH_anon_WITH_AES_256_CBC_SHA
javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.223 
UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite: 
TLS_DH_anon_WITH_AES_256_CBC_SHA
javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.223 
UTC|SSLContextImpl.java:399|Ignore disabled cipher suite: 
TLS_DH_anon_WITH_AES_128_CBC_SHA256
javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.224 
UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite: 
TLS_DH_anon_WITH_AES_128_CBC_SHA256
javax.net.ssl|FINE|01|main|2023-03-03 16:43:22.224 
UTC|SSLContextImpl.java:399|Ignore disabled cipher suite: 
TLS_ECDH_anon_WITH_AES_128_CBC_SHA
javax.net.ssl|ALL|01|main|2023-03-03 16:43:22.224 
UTC|SSLContextImpl.java:408|Ignore unsupported cipher suite: 
TLS_ECDH_anon_WITH_AES_128_

Fw: Apache Tomcat 10.1.6 is giving me java.lang.ClassNotFoundException: jakarta.servlet.jsp.JspFactory

2023-03-03 Thread Karen Goh 
 Hi experts,
I am not getting reply on this jakarta.servlet.jsp.JspFactory, can I have some 
feedback how to make Tomcat works with the libraries I need ?
Tks & rgds,Karen

   - Forwarded Message - From: Karen Goh To: 
users@tomcat.apache.org Sent: Thursday, March 2, 2023 
at 01:24:47 PM GMT+8Subject: Re: Apache Tomcat 10.1.6 is giving me 
java.lang.ClassNotFoundException: jakarta.servlet.jsp.JspFactory
  Hi Chris,
I have forwarded you that SO URL to showed you that the scope provided needed 
to add it in but after you pointed out I realised it is wrong.
Nope.  I am not using jetty run. I right click on Eclipse run on server.

So, the latest happening is that I got an advice from another SO user to put in 
the jar from Download jakarta.servlet.jsp-api JAR file with all dependencies
I tried to exploded the jar to see if it contains all the dependencies I need 
but all i could find is byte code .class.


| 
| 
|  | 
Download jakarta.servlet.jsp-api JAR file with all dependencies

Download jakarta.servlet.jsp-api JAR file ✓ With dependencies ✓ Documentation ✓ 
Source code
 |

 |

 |

and Tomcat is able to run.  Only thing is that the index.jsp doesn't show up. 
It only show localhost:8080/webclientv1/ and the browser appears moving like 
waiting.

But, still I got to sort out the dependencies cos I need them for CICD.

Could you advise me what is the full set of dependencies I need ?


Tks.


On Thursday, March 2, 2023 at 01:51:56 AM GMT+8, Christopher Schultz 
 wrote:  
 
 Karen,

On 3/1/23 10:21 AM, Karen Goh wrote:
>  hi Chris,
> I am following advice from ClassNotFoundException: 
> javax.servlet.jsp.JspFactory
> ClassNotFoundException: javax.servlet.jsp.JspFactory
> 
> I have a maven-based app that I copied exactly and tried to run mvn jetty:run 
> And now getting this error:Cau...
> 
>   where it says scope provided must be added
> Anwyay, I have removed the scope and the jars that are put in the lib folder 
> in WEB-INF, it is no use.
> The same error still persists.
> I removed provided on all the Jakarat ee replated dependencies 
> as shown in the pom just now.
> Hope you could advise me now.
> Tks.

If you are using jetty:run then you are probably not using Tomcat. >:|

-chris

>      On Wednesday, March 1, 2023 at 10:19:18 PM GMT+8, Christopher Schultz 
> wrote:
>  
>  Karen,
> 
> On 3/1/23 09:09, Karen Goh wrote:
>> Hello experts,
>> I need desperate help to fix this java.lang.ClassNotFoundException: 
>> jakarta.servlet.jsp.JspFactory
>> Here are my dependencies which I have installed but still Tomcat will still 
>> purge out the ClassNotFound error :
>> 
>>            
>>                com.fasterxml.jackson.core
>>                jackson-databind
>>                2.13.3
>>            
>>            
>>            
>>                com.squareup.retrofit2
>>                retrofit
>>                2.9.0
>>            
>>            
>>                com.squareup.retrofit2
>>                converter-gson
>>                2.9.0
>>            
>>            
>>            
>>                com.google.code.gson
>>                gson
>>                2.10.1
>>            
>>            
>>            
>>                jakarta.servlet.jsp.jstl
>>                jakarta.servlet.jsp.jstl-api
>>                3.0.0
>>                provided
>>            
>>            
>>            
>>                jakarta.platform
>>                jakarta.jakartaee-web-api
>>                10.0.0
>>                provided
>>            
>>                
>>                jakarta.servlet
>>                jakarta.servlet-api
>>                6.0.0
>>                provided
>>            
>>            
>>                org.glassfish.web
>>                jakarta.servlet.jsp.jstl
>>                3.0.1
>>                provided
>>            
>>            
>>        jakarta.el
>>        jakarta.el-api
>>        5.0.0
>>        provided
>>        
>>            
>> I have even attached the jar - jakarta.servlet.jsp.jstl-3.0.1.jar
>> jakarta.servlet.jsp.jstl-api-3.0.0.jarto the lib folder.
>> Java 17, Eclipse on Windows 10.
>> I am not sure how to tackle this problem, as I need to get an assignment 
>> done.Would appreciate advice from this group.Tks.
> 
> Your POM shows both jstl artifacts as "provided" meaning they won't be
> downloaded and bundled into your application. I think you actually need
> to allow those to be downloaded as they are not provided by Tomcat (I
> think! I'm no JSTL expert).
> 
> But Tomcat definitely ships with a copy of
> jakarta.servlet.jsp.JspFactory so if you are adding a JAR which contains
> that class, you are likely causing a conflict.
> 
> Tomcat really should be prohibiting that class from being provided by an
> application, but maybe you have put it somewhere that is confusing the JVM.
> 
> Which lib/ folder did you put those JARs into?
> 
> -chris
> 
> -
> To unsubscrib

[ANN] Apache Tomcat 9.0.73 available

2023-03-03 Thread Rémy Maucherat 
The Apache Tomcat team announces the immediate availability of Apache
Tomcat 9.0.73.

Apache Tomcat 9 is an open source software implementation of the Java
Servlet, JavaServer Pages, Java Unified Expression Language, Java
WebSocket and JASPIC technologies.

Apache Tomcat 9.0.73 is a bugfix and feature release. The notable
changes compared to 9.0.72 include:

- Correct a regression introduced in the fix for bug
  66196 that meant that the HTTP headers and/or request line
  could get corrupted (one part overwriting another part) within a single
  request.

- Provide a more appropriate response (501 rather than 400) when rejecting
  an HTTP request using the CONNECT method.

- Add support for txt: and rnd: rewrite map types from mod_rewrite. Based
  on a pull request provided by Dimitrios Soumis.

Along with lots of other bug fixes and improvements.

Please refer to the change log for the complete list of changes:
https://tomcat.apache.org/tomcat-9.0-doc/changelog.html


Downloads:
https://tomcat.apache.org/download-90.cgi

Migration guides from Apache Tomcat 7.x and 8.x:
https://tomcat.apache.org/migration.html

Enjoy!

- The Apache Tomcat team

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 9 crashes because of a Windows update

2023-03-03 Thread Mark Thomas 

On 03/03/2023 07:57, Katie S wrote:

Mark,

The logs say the following:
[2023-03-03 08:25:59] [info]  [ 6836] Apache Commons Daemon procrun 
(1.2.1.0 64-bit) started.

[2023-03-03 08:25:59] [info]  [ 6836] Running Service 'BOEXI40Tomcat'...
[2023-03-03 08:25:59] [info]  [ 7696] Starting service...
[2023-03-03 08:26:00] [info]  [ 7696] Service started in 1187 milliseconds.
[2023-03-03 08:27:53] [info]  [ 6836] Run service finished.
[2023-03-03 08:27:53] [info]  [ 6836] Apache Commons Daemon procrun 
finished.


08:25 was the time I've run Tomcat and 08:27 was the time Tomcat stopped 
working by himself.


OK that looks normal.


I've enclosed the stderr.log to this email.


The mailing list strips attachments. You either need to paste the 
contents in the body of the email or use a file sharing service (that 
doesn't require an account to read the files).


We need to see the rest of the log files. I suggest the following:

- delete (or move) all the existing logs
- configure Commons Daemon for debug logging
- start the Tomcat service
- wait for the service to stop

Provide us with all the logs.

Thanks,

Mark



- Katie


Le jeu. 2 mars 2023 à 15:09, Mark Thomas > a écrit :


On 02/03/2023 13:59, Katie S wrote:
 > I'm using the Central Configuration Manager from Business Objects
4.0.
 > I start Apache Tomcat for BI4, it says "running" and then after a
 > few minutes and without any action, the status becomes "stopped".

OK.

What do the logs show?

Mark


 >
 > - Katie
 >
 > Le jeu. 2 mars 2023 à 11:10, Mark Thomas mailto:ma...@apache.org>> a écrit :
 >
 >> On 02/03/2023 08:49, Katie S wrote:
 >>> Sorry for being unclear and thank you for your answer.
 >>>
 >>> I can start Tomcat but after a few minutes it stops working. And
 >> everytime
 >>> I restart it, the behavior is the same.
 >>
 >> Again, define "stops working".
 >>
 >> Mark
 >>
 >>>
 >>> - Katie
 >>>
 >>> Le jeu. 2 mars 2023 à 09:39, Mark Thomas mailto:ma...@apache.org>> a écrit :
 >>>
  On 02/03/2023 08:28, Katie S wrote:
 > Hello,
 >
 > Do you have any information on Tomcat 9 not working after
some Windows
 > Updates ?
 > We have installed the KB5022838 on our Windows Server 2016
Standard and
 > since this we can restart Tomcat but it stops working after
only few
 > minutes.
 
  Define "stops working". The subject says "crashes". We need
specifics.
 
 > We are sure about the fact that the Windows update is guilty
as it
 >> worked
 > properly when we restored the VMware snapshot.
 
  That is a useful data point.
 
  Mark
 
 
-
  To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org

  For additional commands, e-mail: users-h...@tomcat.apache.org

 
 
 >>>
 >>
 >>
-
 >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org

 >> For additional commands, e-mail: users-h...@tomcat.apache.org

 >>
 >>
 >

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org

For additional commands, e-mail: users-h...@tomcat.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org