On 17/06/2025 17:29, Mark Thomas wrote:
In short, you'll probably need to increase maxPartCount
Thanks, thats fixed it.
Stephen
==
|epcc| Dr Stephen P Booth Principal Architect
See https://bz.apache.org/bugzilla/show_bug.cgi?id=69710
In short, you'll probably need to increase maxPartCount
Mark
On 17/06/2025 16:45, Stephen Booth wrote:
I just updated my production servers from 9.0.104 to 9.0.106
and this broke my registration form with the following exception.
Stack
I just updated my production servers from 9.0.104 to 9.0.106
and this broke my registration form with the following exception.
Stack Trace:
org.apache.tomcat.util.http.fileupload.impl.FileCountLimitExceededException:
attachment
at
org.apache.tomcat.util.http.fileupload.FileUploadBase
The issue occurred again in Tomcat v10.1.40 but is fixed again in Tomcat
v10.1.41
On Thu, Apr 3, 2025 at 7:52 PM Mark Thomas wrote:
> On 03/04/2025 05:34, Tim N wrote:
> > That should have been
> >> Looks like this last worked Tomcat v10.1.20 and first failed v10.1.23
> >
> > ...and now looks li
On 03/04/2025 05:34, Tim N wrote:
That should have been
Looks like this last worked Tomcat v10.1.20 and first failed v10.1.23
...and now looks like this was first fixed again in v10.1.39
Any ideas why?
It suggests that the JasperInitializer was not trigger on start. If not
a packaging issu
That should have been
> Looks like this last worked Tomcat v10.1.20 and first failed v10.1.23
...and now looks like this was first fixed again in v10.1.39
Any ideas why?
On Sat, Feb 8, 2025 at 6:36 AM Tim N wrote:
> Looks like this last worked Tomcat v10.1.20 and first failed v19.1.23
>
> On F
> >>>>
> >>>> We run tomcat on java17 with the embedded tomcat setup.
> >>>> We have http and https connectors and we have http2 upgradeProtocol
> for
> >>>> both.
> >>>>
> >>>> We recently upgraded from
upgradeProtocol for
both.
We recently upgraded from 9.0.88 to 10.1.24 to work on javax to jakarta
migration, and after a while, upgraded to 10.1.33.
After the upgrade, we started to see random and rare 500 errors for
some of
the http2 GET requests over https.
When reproducing the error on our
from 9.0.88 to 10.1.24 to work on javax to jakarta
migration, and after a while, upgraded to 10.1.33.
After the upgrade, we started to see random and rare 500 errors for
some of
the http2 GET requests over https.
When reproducing the error on our development machines, we could see the
following
to jakarta
migration, and after a while, upgraded to 10.1.33.
After the upgrade, we started to see random and rare 500 errors for some of
the http2 GET requests over https.
When reproducing the error on our development machines, we could see the
following trace on the server
; >
> > We recently upgraded from 9.0.88 to 10.1.24 to work on javax to jakarta
> > migration, and after a while, upgraded to 10.1.33.
> > After the upgrade, we started to see random and rare 500 errors for some
> of
> > the http2 GET requests over https.
> > Whe
igration, and after a while, upgraded to 10.1.33.
> After the upgrade, we started to see random and rare 500 errors for some of
> the http2 GET requests over https.
> When reproducing the error on our development machines, we could see the
> following trace on the server:
> ```
>
On Thu, Feb 13, 2025 at 9:58 AM Rainer Jung wrote:
> Am 13.02.25 um 09:40 schrieb Cenk Pekyaman:
> ...
>
> > We can reproduce the issue somewhat reliably with the reproducer setup we
> > have in https://github.com/cpekyaman/java-server-http2-test.
> > The odd part is we could only reproduce it wi
Am 13.02.25 um 09:40 schrieb Cenk Pekyaman:
...
We can reproduce the issue somewhat reliably with the reproducer setup we
have in https://github.com/cpekyaman/java-server-http2-test.
The odd part is we could only reproduce it with certain clients reliably,
with go and curl (we include go client
We run tomcat on java17 with the embedded tomcat setup.
We have http and https connectors and we have http2 upgradeProtocol for
both.
We recently upgraded from 9.0.88 to 10.1.24 to work on javax to jakarta
migration, and after a while, upgraded to 10.1.33.
After the upgrade, we started to see
Looks like this last worked Tomcat v10.1.20 and first failed v19.1.23
On Fri, Feb 7, 2025 at 3:22 PM Tim N wrote:
> I was launching my application successfully with Tomcat 10.1.16 using a
> JAR with all dependencies in a single JAR via "maven-assembly-plugin".
>
> Since upgrading to Tomcat 10.1.
I was launching my application successfully with Tomcat 10.1.16 using a JAR
with all dependencies in a single JAR via "maven-assembly-plugin".
Since upgrading to Tomcat 10.1.34, one of my applications is now throwing
java.lang.NullPointerException: Cannot invoke
"org.apache.jasper.compiler.TldCac
Am 30. August 2024 16:20:24 MESZ schrieb Mark Thomas :
>On 30/08/2024 15:15, Kenan, John wrote:
>> Apache Tomcat Security Team:
Hi,
>> Please advise when an update to Apache Tomcat will be released that
>> addresses the following Curl and libcurl security vulnerabilities:
>
>What makes you t
On 30/08/2024 15:15, Kenan, John wrote:
Apache Tomcat Security Team:
Please advise when an update to Apache Tomcat will be released that addresses
the following Curl and libcurl security vulnerabilities:
What makes you think Tomcat has a dependency on Curl and/or libcurl?
Mark
Critical:
John,
On 8/30/24 10:15, Kenan, John wrote:
Please advise when an update to Apache Tomcat will be released that
addresses the following Curl and libcurl security vulnerabilities:
Critical:
CVE-2023-38545
High:
CVE-2024-7264
Medium:
CVE-2023-46218
CVE-2023-46219
CVE-2024-0853
Low:
CVE-2023-385
Apache Tomcat Security Team:
Please advise when an update to Apache Tomcat will be released that addresses
the following Curl and libcurl security vulnerabilities:
Critical:
CVE-2023-38545
High:
CVE-2024-7264
Medium:
CVE-2023-46218
CVE-2023-46219
CVE-2024-0853
Low:
CVE-2023-38546
Thank you,
Kalaivani,
On 5/13/24 06:13, GANESAN, Kalaivani wrote:
I have a question regarding upgrading to 9.0.86.
The current version is 9.0.8 and needs to be upgraded to 9.0.86.
We have apache tomcat running in our openptk servers.
Do you have any detailed steps on the process?
We have downloaded apache
Hi,
I have a question regarding upgrading to 9.0.86.
The current version is 9.0.8 and needs to be upgraded to 9.0.86.
We have apache tomcat running in our openptk servers.
Do you have any detailed steps on the process?
We have downloaded apache-tomcat-9.0.86.tar.gz.
Thanks,
Kalaivani G
t; We have experienced the same problem with Tomcat 8.5.94.
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> >> For additional commands, e-mail: users-h...@tomcat.apache.org
&g
times as this is blocking bug for
upgrading to the last Tomcat version:
https://bz.apache.org/bugzilla/show_bug.cgi?id=67670
We understand that it is blocking, but if you re using h2, especially
exposed directly to the internet, you should upgrade to the broken
release and use Konstantin&#
Am 11.10.23 um 14:02 schrieb Alexander Veit:
Caused by: org.apache.http.ConnectionClosedException: Premature end of
Content-Length delimited message body (expected: 4,999; received: 3,040)
at
org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178)
Caused by: org.apache.http.ConnectionClosedException: Premature end of
Content-Length delimited message body (expected: 4,999; received: 3,040)
at
org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:178)
at io.restassured.internal.util.IOUtils.toBy
> Amit
> -Original Message-
> From: Konstantin Kolinko
> Sent: Tuesday, October 10, 2023 7:11 PM
> To: Tomcat Users List
> Subject: Re: [External] Re: Tomcat upgrade from 9.0.80 to 9.0.81
>
>
> CAUTION: This email originated from outside the organization. Do not clic
form (black box) testing and communicate the results (Details in case of
>> failures).
Thanks,
Amit
-Original Message-
From: Konstantin Kolinko
Sent: Tuesday, October 10, 2023 7:11 PM
To: Tomcat Users List
Subject: Re: [External] Re: Tomcat upgrade from 9.0.80 to 9.0.81
CAUTION: This
ср, 11 окт. 2023 г. в 02:31, Amit Pande :
>
> Thank you Konstantin for the quick update!
>
> Since this release contained multiple security fixes, it's important to
> upgrade. However, there seem regressions too.
>
> What is the way forward here? Follow up version c
Thank you Konstantin for the quick update!
Since this release contained multiple security fixes, it's important to
upgrade. However, there seem regressions too.
What is the way forward here? Follow up version coming sooner? Or a version
with just security fixes and all other changes can
Hi!
Thank you for the report.
This issue is known and has already been fixed. See
https://bz.apache.org/bugzilla/show_bug.cgi?id=67664
Best regards,
Konstantin Kolinko
вт, 10 окт. 2023 г. в 23:42, Michael Hayes :
>
> I have just upgraded a working Tomcat 10.1.13 installation to Tomcat 10.1.14,
Hi!
Thank you for reporting and investigating the issue.
I added your observation to
https://bz.apache.org/bugzilla/show_bug.cgi?id=67670
Best regards,
Konstantin Kolinko
ср, 11 окт. 2023 г. в 00:01, Amit Pande :
>
> I am still investigating more but after upgrading from Tomcat 9.0.80 to
> 9.
I am still investigating more but after upgrading from Tomcat 9.0.80 to 9.0.81,
many of our rest assured based tests are failing with below error ...
Caused by: org.apache.http.ConnectionClosedException: Premature end of
Content-Length delimited message body (expected: 4,999; received: 3,040)
I have just upgraded a working Tomcat 10.1.13 installation to Tomcat 10.1.14,
on Rocky Linux 9.2, PostgreSQL 11.20, JDBC driver 42.6.0, Java 17.0.8.
During startup I get this exception:
java.sql.SQLException
at
org.apache.tomcat.jdbc.pool.ConnectionPool.setupConnection(ConnectionPool.jav
On 10/10/2023 13:38, a.grub...@bluewin.ch wrote:
Dear all
I have a question.
When I deploy a new application (either downgrade or upgrade), what is
mandatory to be done apart from ReleaseNotes for the application? I ask
specific for remove certain directories from Tomcat structure, also topic
Dear all
I have a question.
When I deploy a new application (either downgrade or upgrade), what is
mandatory to be done apart from ReleaseNotes for the application? I ask
specific for remove certain directories from Tomcat structure, also topic
remove cache on the directories. Tried to
gt; Subject: Re: SOAP HTTP error: "HTTP/1.1 400 Bad Request" after upgrade to
> 8.5.89.
>
> On 02/06/2023 21:00, jonmcalexan...@wellsfargo.com.INVALID wrote:
> > Good afternoon,
> >
> > Have a team that just upgraded to 8.5.89 from 8.5.72 and started getting
>
On 02/06/2023 21:00, jonmcalexan...@wellsfargo.com.INVALID wrote:
Good afternoon,
Have a team that just upgraded to 8.5.89 from 8.5.72 and started getting these
messages in the logs:
[2023/06/01][01:05:10.012] : [INIT] - EPMSend (init) - EPMSend = SOAP
[2023/06/01][01:05:10.012] : [INIT] - EPM
tomcat.apache.org
> Subject: Re: SOAP HTTP error: "HTTP/1.1 400 Bad Request" after upgrade to
> 8.5.89.
>
>
>
> On 6/2/23 14:00, jonmcalexan...@wellsfargo.com.INVALID wrote:
> > Good afternoon,
> >
> > Have a team that just upgraded to 8.5.
On 6/2/23 14:00, jonmcalexan...@wellsfargo.com.INVALID wrote:
Good afternoon,
Have a team that just upgraded to 8.5.89 from 8.5.72 and started getting these
messages in the logs:
[2023/06/01][01:05:10.012] : [INIT] - EPMSend (init) - EPMSend = SOAP
[2023/06/01][01:05:10.012] : [INIT] - EPMS
Good afternoon,
Have a team that just upgraded to 8.5.89 from 8.5.72 and started getting these
messages in the logs:
[2023/06/01][01:05:10.012] : [INIT] - EPMSend (init) - EPMSend = SOAP
[2023/06/01][01:05:10.012] : [INIT] - EPMSend (init) - SOAPPort = 8443
[2023/06/01][01:05:10.012] : [INIT] -
Mark,
Points noted. Thank you good sir.
I will try the weird path -- just to see if it solves the problem. I am
investigating how it became like this. I inherited this task.
Overall I absolutely concur with going with the an Official Tomcat release.
I want to bring over any / all customized
18 May 2023 06:06:04 Meltron Kendrick :
I created a "jar" file using WinRAR -- but no go ---
Got the following error message...
"Error: Could not find or load main class
org.apache.catalina.util.ServerInfo"
Any ideas on HOW TO properly do this?
Start with an official Tomcat release that d
This might be helpful:
https://docs.oracle.com/en/java/javase/17/docs/specs/man/jar.html
-Terence Bandoian
On 5/17/2023 11:06 PM, Meltron Kendrick wrote:
I created a "jar" file using WinRAR -- but no go ---
Got the following error message...
"Error: Could not find or load main class
org.apa
I created a "jar" file using WinRAR -- but no go ---
Got the following error message...
"Error: Could not find or load main class
org.apache.catalina.util.ServerInfo"
Any ideas on HOW TO properly do this?
On Wed, May 17, 2023 at 9:58 PM Meltron Kendrick
wrote:
> I was able to DECOMPRESS th
I was able to DECOMPRESS the .jar file -- using 7-zip -- and edited the
org/apache/catalina/util/ServerInfo.properties file to the proper version
and date info...
Now I need to COMPRESS everything with the updated
org/apache/catalina/util/ServerInfo.properties
file added back into the .jar file...
Thank you Chuck!
What is the best way to go about updating the 3 lines to accurately reflect
the proper version details?
On Tue, May 16, 2023 at 9:08 PM Chuck Caldarale wrote:
>
> > On 2023-05-16, at 17:02, Meltron Kendrick
> wrote:
> >
> > I am trying to get these fields to UPDATE properly.
> On 2023-05-16, at 17:02, Meltron Kendrick wrote:
>
> I am trying to get these fields to UPDATE properly...
>
> ESPECIALLY THESE 3 ---
> (but all of them would be nice)
>
> Server version: Secure Web Server
> Server built: Jan 01 2000 00:00:00 UTC
> Server number: 1.0.0.0
This informati
I am trying to get these fields to UPDATE properly...
ESPECIALLY THESE 3 ---
(but all of them would be nice)
Server version: Secure Web Server
Server built: Jan 01 2000 00:00:00 UTC
Server number: 1.0.0.0
*sudo -u tomcat /opt/tomcat/bin/version.sh*
Using CATALINA_BASE: /opt/tomcat
Using
t wrote:
> > Hi Meltron,
> >
> >> -Original Message-
> >> From: Meltron Kendrick
> >> Sent: 11 May, 2023 19:09
> >> To: users@tomcat.apache.org
> >> Subject: Best Practice to Upgrade Apache Tomcat from 9.0.56 to 9.0.74
> >>
André,
On 5/11/23 14:49, Andr? van der Lugt wrote:
Hi Meltron,
-Original Message-
From: Meltron Kendrick
Sent: 11 May, 2023 19:09
To: users@tomcat.apache.org
Subject: Best Practice to Upgrade Apache Tomcat from 9.0.56 to 9.0.74
I have NOT been able to locate clear HOW TO steps for
We make official install packages out of each release and then use the
OS package management to do an "official" installation upgrade. This
allows for rollback/downgrade in the event of an issue and allows us to
easily repeat this on the 120+ tomcat servers that we run.
Evan.
On
> -Original Message-
> From: kmhun...@gmail.com <mailto:kmhun...@gmail.com> <mailto:kmhun...@gmail.com>>
> Sent: Thursday, May 11, 2023 3:12 PM
> To: 'Tomcat Users List' <mailto:users@tomcat.apache.org>>
> Subject: RE: Best Practice to Upgr
#x27;Tomcat Users List'
> Subject: RE: Best Practice to Upgrade Apache Tomcat from 9.0.56 to 9.0.74
>
> Not sure if anyone cares or not but this is how I handle...
>
> Unpack Tomcat to /opt/Apache/tomcat/apache-tomcat-
> Create a link for the instance: /opt/Apache/tomcat/current -&g
ary content you just need to copy over the relevant configuration
from the old to the new. Works for my purposes anyway.
-Original Message-
From: Andr? van der Lugt
Sent: Thursday, May 11, 2023 2:49 PM
To: Tomcat Users List
Subject: RE: Best Practice to Upgrade Apache Tomcat from 9.0.56
Hi Meltron,
> -Original Message-
> From: Meltron Kendrick
> Sent: 11 May, 2023 19:09
> To: users@tomcat.apache.org
> Subject: Best Practice to Upgrade Apache Tomcat from 9.0.56 to 9.0.74
>
> I have NOT been able to locate clear HOW TO steps for this.
>
> I am
for
your cooperation.
> -Original Message-
> From: Meltron Kendrick
> Sent: Thursday, May 11, 2023 12:09 PM
> To: users@tomcat.apache.org
> Subject: Best Practice to Upgrade Apache Tomcat from 9.0.56 to 9.0.74
>
> I have NOT been able to locate clear HOW TO step
I have NOT been able to locate clear HOW TO steps for this.
I am currently focused on MINOR upgrades.
I will commence a different thread when I raise the question for MAJOR
upgrades --- say from 9.x to 10.x -- or 9.x to 11.x
IF someone can point me to a great resource...
That would be tremendou
I chose option 1 and re-wrote everything. It was fun
Kevin Huntly
Email: kmhun...@gmail.com
Cell: 716/424-3311
-BEGIN GEEK CODE BLOCK-
Version: 1.0
GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E---
W
Kevin,
On 4/17/23 17:56, Kevin Huntly wrote:
I'm getting the following exception when I try to access my webapp:
17-Apr-2023 17:52:55.982 SEVERE [catalina-exec-1]
org.apache.catalina.core.ApplicationDispatcher.invoke Servlet.service() for
servlet [jsp] threw exception
java.lang.ClassNo
On 4/17/2023 6:13 PM, Kevin Huntly wrote:
Thank you, all set. I guess I wasn't googling the right things lol, either
that or I'm getting a little too used to asking on the list =(
Yes.
-Terence Bandoian
On Mon, Apr 17, 2023 at 7:03 PM Torsten Krah wrote:
The whole thing is also well answe
Just another quick question... and it may not be able to be answered here...
Is there a way to get Eclipse to stop bitching about missing
"javax.servlet.*" dependencies? It's complaining on every JSP I have...
Kevin Huntly
Email: kmhun...@gmail.com
Thank you, all set. I guess I wasn't googling the right things lol, either
that or I'm getting a little too used to asking on the list =(
Kevin Huntly
Email: kmhun...@gmail.com
Cell: 716/424-3311
---
The whole thing is also well answered there btw:
https://stackoverflow.com/questions/4928271/how-to-install-jstl-the-absolute-uri-http-java-sun-com-jstl-core-cannot-be-r#4928309
Kevin Huntly schrieb am Di., 18. Apr. 2023, 00:52:
> I am now seeing this:
>
> 17-Apr-2023 18:50:44.450 SEVERE [catal
https://stackoverflow.com/questions/74585710/migration-to-jakarta-ee-unable-to-find-taglib-c-for-uri-jakarta-tags-core
Does that help?
Kevin Huntly schrieb am Di., 18. Apr. 2023, 00:52:
> I am now seeing this:
>
> 17-Apr-2023 18:50:44.450 SEVERE [catalina-exec-1]
> org.apache.catalina.core.App
I am now seeing this:
17-Apr-2023 18:50:44.450 SEVERE [catalina-exec-1]
org.apache.catalina.core.ApplicationDispatcher.invoke Servlet.service() for
servlet [jsp] threw exception
org.apache.jasper.JasperException:
/com.cws.esolutions.web.login/jsp/html/en/Login.jsp (line: [1], column:
[1])
And update your taglib definitions, see here:
https://jakarta.ee/specifications/tags/3.0/
The old ones are deprecated/ removed:
Quote:
Rename java.sun.com taglib URIs to new jakarta.tags.* URNs.
Kevin Huntly schrieb am Di., 18. Apr. 2023, 00:34:
> Now i'm getting these:
>
> 17-Apr-2023 18:
https://jakarta.ee/specifications/tags/3.0/tagdocs/c/tld-summary.html
. . . just my two cents
/mde/
On 4/17/2023 3:34 PM, Kevin Huntly wrote:
Now i'm getting these:
17-Apr-2023 18:32:03.236 INFO [main]
org.apache.catalina.core.ApplicationContext.log No Spring
WebApplicationInitializer types d
The Jakarta jstl ones have to be compile scope, they are not included in
tomcat, do you have that?
See the migration guide, spec section, only those APIs listed there should
be provided scope.
Kevin Huntly schrieb am Di., 18. Apr. 2023, 00:34:
> Now i'm getting these:
>
> 17-Apr-2023 18:32:03.2
Now i'm getting these:
17-Apr-2023 18:32:03.236 INFO [main]
org.apache.catalina.core.ApplicationContext.log No Spring
WebApplicationInitializer types detected on classpath
17-Apr-2023 18:32:04.904 INFO [main]
org.apache.catalina.core.ApplicationContext.log Initializing Spring
DispatcherServlet 'eS
You should only use https://jakarta.ee/specifications/tags/3.0/ and not the
old 1.2.5 one, remove that old one.
Why do you have both included?
Kevin Huntly schrieb am Di., 18. Apr. 2023, 00:19:
> 6.0.0
>
> 1.2.5
>
> 3.0.0
>
> 3.1.1
>
>
> Kevin Hun
6.0.0
1.2.5
3.0.0
3.1.1
Kevin Huntly
Email: kmhun...@gmail.com
Cell: 716/424-3311
-BEGIN GEEK CODE BLOCK-
Version: 1.0
GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E---
W+++ N+ o K(+) w--- O- M--
All the api ones have to be provided, not compile scope imho. Tomcat does
provide them, don't package them in your war file and double check the
versions from the guide, there is still a class referencing the old API and
is causing the exception.
You missed to add the versions you used, add them h
Thank you for that... I have the right (I think) dependencies in my pom:
org.apache.taglibs
taglibs-standard-impl
${taglibs.version}
jar
compile
jakarta.servlet.jsp.jstl
jakarta.servlet.jsp.jstl-api
${jstl.version}
jar
compile
jakarta.servlet.jsp
jakarta.servlet.jsp-api
${jsp
Please read https://tomcat.apache.org/migration-10.html#Server_Pages_3.0
and while you are there, read the whole guide ;-).
Kevin Huntly schrieb am Mo., 17. Apr. 2023, 23:57:
> Hello,
>
> I'm getting the following exception when I try to access my webapp:
>
> 17-Apr-2023 17:52:55.982 SEVERE [cat
Hello,
I'm getting the following exception when I try to access my webapp:
17-Apr-2023 17:52:55.982 SEVERE [catalina-exec-1]
org.apache.catalina.core.ApplicationDispatcher.invoke Servlet.service() for
servlet [jsp] threw exception
java.lang.ClassNotFoundException:
javax.servlet.jsp.tagext
Hi user group:
just found open-telemetry has fixing for it:
https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/instrumentation/tomcat/tomcat-common/javaagent/src/main/java/io/opentelemetry/javaagent/instrumentation/tomcat/common/TomcatHelper.java#L71
```
static Strin
Hi Mark
I can't find any Valve setting in the spring boot application(search by
valve), would you mind sharing more info?
Regarding the mb state and debugging, yes aware that my local intellij
debugger could change the mb state, so in the the debug lib I call
mb.getType() only
I got more interes
On 17/03/2023 14:27, Rui wrote:
Hi user group:
I added some debug info to the 9.0.71 baseline
from the logs it hit this (supposed not inn 9.0.70)
https://github.com/apache/tomcat/blob/9.0.71/java/org/apache/catalina/connector/CoyoteAdapter.java#L677
That suggests you are using the Rewrite Val
Hi user group:
I added some debug info to the 9.0.71 baseline
from the logs it hit this (supposed not inn 9.0.70)
https://github.com/apache/tomcat/blob/9.0.71/java/org/apache/catalina/connector/CoyoteAdapter.java#L677
means undecodedURI type is T_CHARS or T_STR, however, decodedURI type is
T_NUL
I did some tests with several different commits in 9.0.71, I think my issue
is caused by this
https://github.com/apache/tomcat/commit/10a1a6d46d952bab4dfde44c3c0de12b0330da79
the "toBytesSimple" change has not been added to the repo yet, so the
change in 9.073 doesn't solve the problem.
Next I will
> -Original Message-
> From: Chuck Caldarale
> Sent: Monday, March 6, 2023 1:12 PM
> To: Tomcat Users List
> Subject: Re: health check return 404 after upgrade from 70 to tomcat 9.0.71
>
>
> > On Mar 6, 2023, at 12:03,
> wrote:
> >
> >
> On Mar 6, 2023, at 12:03,
> wrote:
>
> I believe we may have figured out what was causing the issue, but not why it
> was causing it.
>
> In the mod-proxy-http configuration for the balancer, we had been using the
> fully qualified host name in the balancer url. When we switched to IP
>
> -Original Message-
> From: Mark Thomas
> Sent: Monday, March 6, 2023 10:34 AM
> To: users@tomcat.apache.org
> Subject: Re: health check return 404 after upgrade from 70 to tomcat 9.0.71
>
> On 25/02/2023 17:57, Mark Thomas wrote:
> >
> >
> >
On 25/02/2023 17:57, Mark Thomas wrote:
On 25/02/2023 15:47, Rui wrote:
Hi
recently upgraded tomcat to 9.0.71 from 9.0.70
but saw 404 in our EKS cluster(with istio installed)
Received [GET /actuator HTTP/1.1
Host: x:8079
User-Agent: kube-probe/1.23+
Accept: */*
Connection: close
Accept-En
On 25/02/2023 15:47, Rui wrote:
Hi
recently upgraded tomcat to 9.0.71 from 9.0.70
but saw 404 in our EKS cluster(with istio installed)
Received [GET /actuator HTTP/1.1
Host: x:8079
User-Agent: kube-probe/1.23+
Accept: */*
Connection: close
Accept-Encoding: gzip
]
Incoming request /health
Hi
recently upgraded tomcat to 9.0.71 from 9.0.70
but saw 404 in our EKS cluster(with istio installed)
Received [GET /actuator HTTP/1.1
Host: x:8079
User-Agent: kube-probe/1.23+
Accept: */*
Connection: close
Accept-Encoding: gzip
]
Incoming request /health with originalRemoteAddr
in 9.0.
t in the process.
:)
-chris
-Original Message-
From: Christopher Schultz
Sent: Friday, November 18, 2022 14:37
To: users@tomcat.apache.org
Subject: Re: tomcat and FIPS - PKCS11 CKR_SESSION_READ_ONLY error after OpenJDK
upgrade
Joey,
On 11/17/22 10:52, Joey Cochran wrote:
You might
-Original Message-
From: Christopher Schultz
Sent: Friday, November 18, 2022 14:37
To: users@tomcat.apache.org
Subject: Re: tomcat and FIPS - PKCS11 CKR_SESSION_READ_ONLY error after OpenJDK
upgrade
Joey,
On 11/17/22 10:52, Joey Cochran wrote:
> You might still have a passphrase on the p
way before any cipher suites are being negotiated,
so don't aorry about that.
-chris
-Original Message-
From: Cantor, Angela T.
Sent: Wednesday, November 16, 2022 7:28 PM
To: Tomcat Users List
Subject: RE: tomcat and FIPS - PKCS11 CKR_SESSION_READ_ONLY error after OpenJDK
up
Angela,
On 11/16/22 20:31, Cantor, Angela T. wrote:
And one thing I forgot - yes Chris, could you please provide the code
you mentioned in case that is the issue?
Sure:
import java.security.Provider;
import java.security.Security;
import java.util.*;
/**
* A crude class for displaying all th
--
From: Christopher Schultz
Sent: Tuesday, November 15, 2022 21:50
To: users@tomcat.apache.org
Subject: Re: tomcat and FIPS - PKCS11 CKR_SESSION_READ_ONLY error after OpenJDK
upgrade
Angela,
On 11/14/22 11:56, Cantor, Angela T. wrote:
We just upgraded OpenJDK from 17.0.4.0.8-2.el8_6 to the
after OpenJDK
upgrade
Thanks to Joey and Chris for responding.
Joey had said
>Jump through the hoop of rebuilding the keystore with the current java
> I believe this is what we did that made the difference I am not
> familiar with PKCS11
> we use Http11Nio2Protocol wit
And one thing I forgot - yes Chris, could you please provide the code you
mentioned in case that is the issue?
Thanks,
Angela
>> certificateKeystoreProvider="SunPKCS11-NSS-FIPS"
>
>Could this be the problem? Does your new Java version have that security
>provider available
m: Christopher Schultz
Sent: Tuesday, November 15, 2022 21:50
To: users@tomcat.apache.org
Subject: Re: tomcat and FIPS - PKCS11 CKR_SESSION_READ_ONLY error after OpenJDK
upgrade
Angela,
On 11/14/22 11:56, Cantor, Angela T. wrote:
> We just upgraded OpenJDK from 17.0.4.0.8-2.el8_6 to the abov
Angela,
On 11/14/22 11:56, Cantor, Angela T. wrote:
We just upgraded OpenJDK from 17.0.4.0.8-2.el8_6 to the above version. Now
tomcat won't listen on the desired port. Something is wonky with it accessing
the keystore. If you all see anything obvious, could you please advise?
Especially i
complete chain bundling.
Hope this helps.
-Joey
-Original Message-
From: Cantor, Angela T.
Sent: Monday, November 14, 2022 10:56 AM
To: users@tomcat.apache.org
Subject: tomcat and FIPS - PKCS11 CKR_SESSION_READ_ONLY error after OpenJDK
upgrade
Hi all,
We have
- tomcat 9.0.68
- RHEL 8.6
Hi all,
We have
- tomcat 9.0.68
- RHEL 8.6 with FIPS
- OpenJDK 17.0.5.0.8-2.el8_6
We just upgraded OpenJDK from 17.0.4.0.8-2.el8_6 to the above version. Now
tomcat won't listen on the desired port. Something is wonky with it accessing
the keystore. If you all see anything obvious, could you
i would normally do a diff between your current version and the next
tomcat version you want to upgrade to and go through the diff slowly.
it is better to be careful and note the changes than sorry later.
On Wed, Oct 5, 2022 at 9:17 PM Mark Thomas wrote:
>
>
>
> On 05/10/2022 09:17,
1 - 100 of 970 matches
Mail list logo
