Thorsten,
On 5/2/25 2:49 PM, Thorsten Heit wrote:
please excuse the long delay in answering (unplanned holidays...)
Tomcat is never going to figure out what MIME type should be used for
a request like "/my/servlet/app?version=!!1.22.32-4-g8a3c060!!"
So I think Mark is probably r
; > application works as expected with the latest Tomcat 10.1.40. But our
> > application does not work with Tomcat 11.0.6 because file upload
> (multipart
> > processing is broken).
> >
> > Apache wicket 10.x uses fileupload2.jakarta.servlet5 thus I create a
> br
Hi Chris,
please excuse the long delay in answering (unplanned holidays...)
Tomcat is never going to figure out what MIME type should be used for a
request like "/my/servlet/app?version=!!1.22.32-4-g8a3c060!!"
So I think Mark is probably right (well, he's right like 99.999% o
Ernesto,
On 5/1/25 8:51 PM, Ernesto Reinaldo Barreiro wrote:
We have an Apache Wicket application that I just ported to wicket 10. The
application works as expected with the latest Tomcat 10.1.40. But our
application does not work with Tomcat 11.0.6 because file upload (multipart
processing is
short window from when tomcat creates a new
session and when it is persisted to db which under heavy loads
duplicates can be created.
Each node generates a session identifier for itself, and the (default)
session id space is quite large (2^128 bits or
340282366920938463463374607431768211456
Hi,
Thank you very much for your email. My answers inlined.
On Fri, May 2, 2025 at 6:54 AM Rick Noel
wrote:
> We had the same issue when going to Tomcat 11.
>
> You need to make two changes.
> 1) get the request params passed in via.
> jakarta.servlet.http.P
We had the same issue when going to Tomcat 11.
You need to make two changes.
1) get the request params passed in via. jakarta.servlet.http.Part
Like so.
import jakarta.servlet.http.Part;
Part fileUpload = request.getPart("param-name");
if(null !=
Thanks Chris,
I appreciate you input. In answer to your questions the primary issue we
are experiencing is that on occasions (once a month or two) we will get
two users on different nodes with the same session id. We suspect this
could be because there is a short window from when tomcat
Hi,
We have an Apache Wicket application that I just ported to wicket 10. The
application works as expected with the latest Tomcat 10.1.40. But our
application does not work with Tomcat 11.0.6 because file upload (multipart
processing is broken).
Apache wicket 10.x uses fileupload2
Minor nit:
Tomcat also supports:
Jakarta Annotations
Jakarta Debugging Support for Other Languages
but we don't list then on the spec age. We probably should.
Mark
On 29/04/2025 15:36, William Crowell wrote:
Chris,
Beautiful answer and exactly what I was looking for. Thank you.
Re
Chris,
Beautiful answer and exactly what I was looking for. Thank you.
Regards,
William Crowell
From: Christopher Schultz
Date: Tuesday, April 29, 2025 at 10:32 AM
To: Tomcat Users List , William Crowell
Subject: Re: When was the first stable GA release of Apache Tomcat 11.0.x?
William
William,
On 4/29/25 7:04 AM, William Crowell wrote:
Just for my clarification: When was the first stable GA release of
Apache Tomcat 11.0.x?
I believe it was October 9th, 2024, but I did see the Jakarta EE
Platform Web Profile 11 was released on March 30th, 2025:
https://projects.eclipse.org
Good morning,
Just for my clarification: When was the first stable GA release of Apache
Tomcat 11.0.x?
I believe it was October 9th, 2024, but I did see the Jakarta EE Platform Web
Profile 11 was released on March 30th, 2025:
https://projects.eclipse.org/projects/ee4j.jakartaee-platform
31650 Apache Tomcat - DoS via invalid HTTP prioritization header
Severity: High
Vendor: The Apache Software Foundation
Versions Affected:
Apache Tomcat 11.0.0-M2 to 11.0.5
Apache Tomcat 10.1.10 to 10.1.39
Apache Tomcat 9.0.76 to 9.0.102
Description:
Incorrect error handling for some invalid
Hi,
I have looked at the commits and all have in changes http2. Is this an
issue in case we don't use http2?
Thank you.
Regards,
Zdenek Henek
On Mon, Apr 28, 2025 at 7:12 PM Mark Thomas wrote:
> CVE-2025-31650 Apache Tomcat - DoS via invalid HTTP prioritization header
>
>
CVE-2025-31651 Apache Tomcat - Rewrite rule bypass
Severity: Low
Vendor: The Apache Software Foundation
Versions Affected:
Apache Tomcat 11.0.0-M1 to 11.0.5
Apache Tomcat 10.1.0-M1 to 10.1.39
Apache Tomcat 9.0.0.M1 to 9.0.102
Description:
For a subset of unlikely rewrite rule configurations
CVE-2025-31650 Apache Tomcat - DoS via invalid HTTP prioritization header
Severity: High
Vendor: The Apache Software Foundation
Versions Affected:
Apache Tomcat 11.0.0-M2 to 11.0.5
Apache Tomcat 10.1.10 to 10.1.39
Apache Tomcat 9.0.76 to 9.0.102
Description:
Incorrect error handling for some
ve a cluster of tomcat servers on AWS EC2 which operate behind
an AWS load balancer with sticky sessions.
We have our session storage on a DB using a JDBC store which for the
most part is working well, but we occasionally see duplicate session
ids which create issues where a new session with a duplic
Rick,
On 4/24/25 10:47 AM, Rick Noel wrote:
Hello,
When I upgraded to tomcat 11.0.5 and Java 24,
Tomcat log gives this warning..
WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
WARNING: sun.misc.Unsafe::invokeCleaner has been called by
Hello,
When I upgraded to tomcat 11.0.5 and Java 24,
Tomcat log gives this warning..
WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
WARNING: sun.misc.Unsafe::invokeCleaner has been called by
org.apache.tomcat.util.buf.ByteBufferUtilsUnsafe
(file:/home/web
On 24/04/2025 02:02, Zoran Avtarovski wrote:
We have a cluster of tomcat servers on AWS EC2 which operate behind
an AWS load balancer with sticky sessions.
We have our session storage on a DB using a JDBC store which for the
most part is working well, but we occasionally see duplicate session
On 24/04/2025 02:02, Zoran Avtarovski wrote:
We have a cluster of tomcat servers on AWS EC2 which operate behind an
AWS load balancer with sticky sessions.
We have our session storage on a DB using a JDBC store which for the
most part is working well, but we occasionally see duplicate session
. Does anyone know why they aren't supported?
Z.
On 24/4/2025 11:20 am, Chuck Caldarale wrote:
On 2025 Apr 23, at 20:02, Zoran Avtarovski wrote:
We have a cluster of tomcat servers on AWS EC2 which operate behind an AWS load
balancer with sticky sessions.
We have our session storage on
> On 2025 Apr 23, at 20:02, Zoran Avtarovski wrote:
>
> We have a cluster of tomcat servers on AWS EC2 which operate behind an AWS
> load balancer with sticky sessions.
>
> We have our session storage on a DB using a JDBC store which for the most
> part is working well
We have a cluster of tomcat servers on AWS EC2 which operate behind an
AWS load balancer with sticky sessions.
We have our session storage on a DB using a JDBC store which for the
most part is working well, but we occasionally see duplicate session ids
which create issues where a new session
On 4/17/25 4:56 PM, Mark Thomas wrote:
> On 17/04/2025 20:32, RAY, DAVID wrote:
>>> I updated from Tomcat 9.0.102 to 9.0.104 on two RHEL servers. Both
>>> are 'crashing' at startup after the update. Version 9.0.102 and
>>> prior versions ran fine. No
Mark,
On 4/17/25 4:56 PM, Mark Thomas wrote:
On 17/04/2025 20:32, RAY, DAVID wrote:
I updated from Tomcat 9.0.102 to 9.0.104 on two RHEL servers. Both
are 'crashing' at startup after the update. Version 9.0.102 and
prior versions ran fine. No issues. Version 9.0.104 is c
rt of Java since Java 22. Availability of
the API will become better with the next Java LTS as users become more
confident about deploying a JVM that supports the API.
>
Is there any update on QUIC transport protocol over HTTP/3 support in Tomcat 11?
Does it have anything to do with JEP draft
Thorsten,
On 4/17/25 1:54 AM, Thorsten Heit wrote:
Hi Chris,
That definitely sounds odd. Do you have anything on the network
between the client (browser) and the server (Tomcat)? Specifically,
anything like a load-balancer, proxy, or similar?
I just want to remove other possible causes
ers in
the same place as my other loggers, in the logback.xml file. I haven't yet
verified this with the Tomcat startup error I was looking at (that was
apparently resolved in some other way), but I've verified that I can see
other log messages from StandardContext, so it's pretty likel
ave a couple hundred Java SpringBoot services, most of them using
SpringBoot 3.2.5. Internally, it is using Tomcat through the
"tomcat-embed-core" artifact, version 10.1.30.
Every once in a while, I run into a problem where the service startup fails
with some variation of this:
Hi Tomcat users,
I'm new in this mailing list but old (very old) Tomcat user (& his close
friend TomEE).
Considering :
-
https://tomcat.apache.org/tomcat-11.0-doc/config/jaspic.html#3rd_party_modules
(Especially Dynamic configuration)
- https://jakarta.ee/specifications/authe
-Original Message-
From: Mark Thomas
Sent: Thursday, April 17, 2025 3:57 PM
To: users@tomcat.apache.org
Subject: Re: Tomcat 9.0.104 Crashing at Startup on RHEL 8.4
On 17/04/2025 20:32, RAY, DAVID wrote:
> I updated from Tomcat 9.0.102 to 9.0.104 on two RHEL servers. Both
On 17/04/2025 20:32, RAY, DAVID wrote:
I updated from Tomcat 9.0.102 to 9.0.104 on two RHEL servers. Both are
'crashing' at startup after the update.Version 9.0.102 and prior versions
ran fine. No issues. Version 9.0.104 is crashing at startup. Any suggestions
much appreciat
I updated from Tomcat 9.0.102 to 9.0.104 on two RHEL servers. Both are
'crashing' at startup after the update.Version 9.0.102 and prior versions
ran fine. No issues. Version 9.0.104 is crashing at startup. Any suggestions
much appreciated:
Method_being_compiled=org/apach
Mark and Rémy,
Thank you for your replies. I think it would be better for now if HTTP/3 is
required is to front Tomcat with NGINX as a reverse proxy.
Regards,
William Crowell
From: Mark Thomas
Date: Thursday, April 17, 2025 at 1:30 PM
To: users@tomcat.apache.org
Subject: Re: Apache Tomcat
7;s a stable regular part of Java since Java 22. Availability of
the API will become better with the next Java LTS as users become more
confident about deploying a JVM that supports the API.
Is there any update on QUIC transport protocol over HTTP/3 support in Tomcat 11?
Being picky, HTTP/3 runs over
2. Availability of
the API will become better with the next Java LTS as users become more
confident about deploying a JVM that supports the API.
> Is there any update on QUIC transport protocol over HTTP/3 support in Tomcat
> 11?
>
> Does it have anything to do with JEP draft 8291976
Hi,
A few questions on the future direction of the project.
It seems like Project Panama is still in preview mode as of JDK 24. Is that
correct?
Is there any update on QUIC transport protocol over HTTP/3 support in Tomcat 11?
Does it have anything to do with JEP draft 8291976?
https
available when the default servlet is
not used.
I should be able to put together a test case for what I think the
problem is but I'd like to be sure it is fixing the problem you are
seeing. There are a couple of options:
1. You test a SNAPSHOT build of Tomcat 10.1.x from the CI system
On 16/04/2025 19:35, Thorsten Heit wrote:
Hi all,
long time Tomcat user, but first time I'm posting, so hi to you all :-)
I'm suffering a strange phenomenon after I upgraded Tomcat on one of our
virtual machines from 10.1.39 to 10.1.40:
When I open the link to an application being
Hi Chris,
That definitely sounds odd. Do you have anything on the network between
the client (browser) and the server (Tomcat)? Specifically, anything
like a load-balancer, proxy, or similar?
I just want to remove other possible causes before diving into Tomcat
(but from your description
Thorsten,
On 4/16/25 2:35 PM, Thorsten Heit wrote:
long time Tomcat user, but first time I'm posting, so hi to you all :-)
I'm suffering a strange phenomenon after I upgraded Tomcat on one of our
virtual machines from 10.1.39 to 10.1.40:
When I open the link to an application be
Hi all,
long time Tomcat user, but first time I'm posting, so hi to you all :-)
I'm suffering a strange phenomenon after I upgraded Tomcat on one of our
virtual machines from 10.1.39 to 10.1.40:
When I open the link to an application being served by Tomcat my browser
(Firefox) now
On Wed, Apr 16, 2025 at 9:14 AM S Abirami
wrote:
>
> Hi All,
>
> After upgrading to Tomcat 11, I noticed Catalina.policy file removed from the
> tomcat.
> I haven't see any specific documentation regarding it in tomcat release note,
> migration guide etc.
The securit
Hi All,
After upgrading to Tomcat 11, I noticed Catalina.policy file removed from the
tomcat.
I haven't see any specific documentation regarding it in tomcat release note,
migration guide etc.
But Gen AI provides the following input, please let me know the following input
is right/wrong?
Dear Tomcat Users/Mark,
I was finally able to retrieve the thread name from the workerThreadName
attribute in RequestProcessor.tomcatExecutor for a request. In order to observe
this, the request had to be long-running, which allowed JMX to capture the
thread’s active state before it completed
The Apache Tomcat team announces the immediate availability of Apache
Tomcat 9.0.104.
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.104 is a bugfix and
Hi,
Is there any current up-to-date documentation on how to setup Apache Tomcat 9
with SAML and Active Directory that is not AI generated?
I know you can do Keycloak IdP with Tomcat, but I was trying to avoid setting
up an identity provider.
I am finding links, but I think there is some
On 03/04/2025 13:05, Rose Mary P T wrote:
HI Mark,
Thanks for your response.
I would like to seek your guidance regarding an issue I am encountering
with my current Tomcat setup. Specifically, your recent suggestions
appear to contradict my existing configuration. Could you kindly confirm
Hi Mark,
I hope this message finds you well.
I just wanted to send a quick reminder regarding the email I sent on 3rd
April,2025 about Monitoring Virtual Threads via JMX / MBeans in Tomcat . If you
haven’t had the chance to review it yet, I would greatly appreciate your
thoughts or any updates
There are several presentations by me on the Tomcat website that discuss
this. Maybe start with this one from slide 12.
Slides:
https://tomcat.apache.org/presentations/2013-02-acna-Apache-Tomcat-Clustering.pdf
Video:
https://www.youtube.com/watch?v=rX1zm11AXcA
HTH,
Mark
On Fri, Apr 4, 2025 at 8:23 P
On 08/04/2025 13:29, Aniket Pachpute wrote:
No Plans.
Please See: https://lists.apache.org/thread/qlzpscgoqct9wspkj5qjkm34s66jswj0
Plans have evolved a little since that message.
For Tomcat 9:
https://lists.apache.org/thread/o8d1nz8mj8dhwq88jbt7zxopp3omkkkb
Work has now started on Tomcat 12
e of the
SSLHostConfig <
https://tomcat.apache.org/tomcat-9.0-doc/config/http.html#SSL_Support_-_SSLHostConfig>
element with the hostName of _default_. If thisSSLHostConfig <
https://tomcat.apache.org/tomcat-9.0-doc/config/http.html#SSL_Support_-_SSLHostConfig>
element is not explicitly
No Plans.
Please See: https://lists.apache.org/thread/qlzpscgoqct9wspkj5qjkm34s66jswj0
On Tue, 8 Apr 2025 at 2:05 PM, Vishwas Bm wrote:
> Hi,
>
> I was looking at the EOL page for tomcat https://endoflife.date/tomcat
> but
> couldn't get information related to EOL dates f
Hi,
I was looking at the EOL page for tomcat https://endoflife.date/tomcat but
couldn't get information related to EOL dates for tomcat 9 and 10.1.
With tomcat11 available now, may I know till what date tomcat 9.0 and
Tomcat 10.1 will be supported ? Is there any specific dates already pl
04/2025 02:42, Chuck Caldarale wrote:
> >
> >> On 2025 Apr 3, at 19:57, Tim N wrote:
> >>
> >> For a long time up to the latest version 11 documentation, there has
> been a
> >> recommended maximum limit of 4 nodes per cluster.
> >>
> >
h attributes from sslhostconfig
> should I
> > use
> > And on internet couldn't find any examples, all of them use clientAuth
>
>
> If you read the 9.0.x documentation for clientAuth, it says this:
>
> clientAuth
> This is an alias for the certificateVerification attr
ientAuth
This is an alias for the certificateVerification attribute of the SSLHostConfig
<https://tomcat.apache.org/tomcat-9.0-doc/config/http.html#SSL_Support_-_SSLHostConfig>
element with the hostName of _default_. If thisSSLHostConfig
<https://tomcat.apache.org/tomcat-9.0
; Hi
> >
> > I'm migrating from tomcat 9 to tomcat 11.0.5
> >
> > I need a client cert validation. Mi server.xml in tomcat 9 :
> >
> >
> > > *keyAlias="karun-tomcat-server-cert"
> >
> >
> > keystoreFile="/home/german/De
> On 2025 Apr 5, at 10:55, juan wrote:
>
> Hi
>
> I'm migrating from tomcat 9 to tomcat 11.0.5
>
> I need a client cert validation. Mi server.xml in tomcat 9 :
>
>
> *keyAlias="karun-tomcat-server-cert"
>
>
> keystoreFile="
Hi
I'm migrating from tomcat 9 to tomcat 11.0.5
I need a client cert validation. Mi server.xml in tomcat 9 :
Adding clientAuth="true" does the trick, and my client has to have a
certificate provided by me.
But in tomcat 11 clientAuth doesn't exist in connector and even r
On 04/04/2025 02:42, Chuck Caldarale wrote:
On 2025 Apr 3, at 19:57, Tim N wrote:
For a long time up to the latest version 11 documentation, there has been a
recommended maximum limit of 4 nodes per cluster.
https://tomcat.apache.org/tomcat-11.0-doc/cluster-howto.html
"This works grea
> On 2025 Apr 3, at 19:57, Tim N wrote:
>
> For a long time up to the latest version 11 documentation, there has been a
> recommended maximum limit of 4 nodes per cluster.
>
> https://tomcat.apache.org/tomcat-11.0-doc/cluster-howto.html
> "This works great for smal
Hi Tim,
If you have an HTTP load balancer that supports "sticky sessions", you can have
a cluster of as many Tomcat instances as you like as backend, without having to
rely on any clustering feature of Tomcat.
Yours,
Reg
> Gesendet: Freitag, den 04.04.2025 um 02:57 Uhr
> Vo
For a long time up to the latest version 11 documentation, there has been a
recommended maximum limit of 4 nodes per cluster.
https://tomcat.apache.org/tomcat-11.0-doc/cluster-howto.html
"This works great for smaller clusters, but we don't recommend it for
larger clusters — more than
HI Mark,
Thanks for your response.
I would like to seek your guidance regarding an issue I am encountering with my
current Tomcat setup. Specifically, your recent suggestions appear to
contradict my existing configuration. Could you kindly confirm whether the
following executor and connector
ditionally, I kept the previous executor and connection configurations for
Tomcat. However, I still do not see any noticeable changes in the
keepAliveCount attribute. The connectionCount currently shows a value of 1.
At this point, I'm unsure of the next troubleshooting steps or what speci
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
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
ly helpful.
Thanks again for your continued support!
Best regards,
Rose Mary
From: Rose Mary P T
Date: Friday, 28 March 2025 at 2:41 PM
To: Tomcat Users List
Subject: [EXTERNAL] RE: Monitoring Virtual Threads via JMX / MBeans in Tomcat
Hi Mark,
Thank you for the confirmation.
As per your suggesti
>
>
>
> jsp
> *.jsp
> *.jspx
> *.vpp
> *.vsp
>
Rick Noel
Systems Programmer | Westwood One
rn...@westwoodone.com
-----Original Message-
From: Rémy Maucherat
Sent: Friday, March 28, 2025 10:56 AM
To: Tomcat Users List
On Fri, Mar 28, 2025 at 3:28 PM Rick Noel wrote:
>
> We recently went from an error free tomcat 10 to the latest tomcat 11.0.5
> And now we get a muiti-part configuration error happening.
>
> The exact error message is this..
>
> org.apache.catalina.core.Applica
We recently went from an error free tomcat 10 to the latest tomcat 11.0.5
And now we get a muiti-part configuration error happening.
The exact error message is this..
org.apache.catalina.core.ApplicationDispatcher.invoke Servlet.service() for
servlet [jsp] threw exception
Hi Mark,
Thank you for the confirmation.
As per your suggestion, I have modified the deployed application so that it no
longer spawns any threads but instead executes a few calls. Additionally, I
kept the previous executor and connection configurations for Tomcat. However, I
still do not see
On 26/03/2025 10:38, Rose Mary P T wrote:
Dear Tomcat Users,
I hope this message finds you well.
As per your previous email, we attempted to fetch the virtual thread count from
the keepAliveCount attribute in the Catalina.ThreadPool MBean.
For context, here is the setup we used:
* We
Dear Tomcat Users,
I hope this message finds you well.
As per your previous email, we attempted to fetch the virtual thread count from
the keepAliveCount attribute in the Catalina.ThreadPool MBean.
For context, here is the setup we used:
* We created a sample Spring Boot application that
Dear Tomcat Users,
I hope this message finds you well.
As per your previous email, we attempted to fetch the virtual thread count from
the keepAliveCount attribute in the Catalina.ThreadPool MBean.
For context, here is the setup we used:
* We created a sample Spring Boot application that
Il 20/03/25 17:16, Christopher Schultz ha scritto:
Roberto,
On 3/20/25 7:52 AM, Roberto Resoli wrote:
Il 19/03/25 20:48, Mark Thomas ha scritto:
On 19/03/2025 18:51, Mark Thomas wrote:
...
So the signing fingerprint may not be the same of that of the
principal key as metioned in the KEYS f
On 3/20/25 9:00 AM, Christopher Schultz wrote:
Is the process still running? My guess is that the old process is never
actually stopping.
FWIW:
I've experienced that situation (i.e., the Tomcat server jobs lingering
after being told to shut down) on IBM Midrange boxes enough times t
file containing
the signing keys for this download
https://dlcdn.apache.org/tomcat/tomcat-9/v9.0.102/bin/apache-
tomcat-9.0.102.tar.gz
Signature: https://downloads.apache.org/tomcat/tomcat-9/v9.0.102/bin/
apache-tomcat-9.0.102.tar.gz.asc
(released this month)
That is:
https://downloads.a
Jason,
On 3/19/25 1:53 PM, Jason Countryman wrote:
Hello,
I'm using Tomcat 10.1.34 on Debian Bookworm. I have a multiple CATALINA_HOME
one CATALINA_BASE configuration, which works perfectly, most of the time.
There are 4 CATALINA_HOME setups.
The issue is that one of these CATALINA
download
https://dlcdn.apache.org/tomcat/tomcat-9/v9.0.102/bin/apache-tomcat-9.0.102.tar.gz
Signature:
https://downloads.apache.org/tomcat/tomcat-9/v9.0.102/bin/apache-tomcat-9.0.102.tar.gz.asc
(released this month)
That is:
https://downloads.apache.org/tomcat/tomcat-9/KEYS
Both the above keys are li
On 19/03/2025 18:51, Mark Thomas wrote:
On 19/03/2025 14:52, Roberto Resoli wrote:
Hello,
I am trying to verify GPG signatures of recent tomcat downloads, but I
noted that both
Mark E D Thomas
DCFD35E0BF8CA7344752DE8B6FB21E8933C60243
Remy Maucherat
On 19/03/2025 14:52, Roberto Resoli wrote:
Hello,
I am trying to verify GPG signatures of recent tomcat downloads, but I
noted that both
Mark E D Thomas DCFD35E0BF8CA7344752DE8B6FB21E8933C60243
Remy Maucherat
48F8E69F6390C9F25CFEDCD268248959359E722B
Are no more available on the https
Hello,
I'm using Tomcat 10.1.34 on Debian Bookworm. I have a multiple CATALINA_HOME
one CATALINA_BASE configuration, which works perfectly, most of the time.
There are 4 CATALINA_HOME setups.
The issue is that one of these CATALINA_BASE setups, when getting the shutdown
command fro
Hello,
I am trying to verify GPG signatures of recent tomcat downloads, but I
noted that both
Mark E D Thomas DCFD35E0BF8CA7344752DE8B6FB21E8933C60243
Remy Maucherat
48F8E69F6390C9F25CFEDCD268248959359E722B
Are no more available on the https://keys.openpgp.org server I use to
look on. Is
Hi Bruno,
On 13.03.2025 21:30, Bruno Melloni wrote:
·This configuration is focused on *Windows* and routes *BOTH Tomcat’s
logging and the web applications logging* to the Tomcat log4j2 config
file.Most examples on the internet are only for one or the other, and
are usually described in Linux
level = ALL
...
java.util.logging.ConsoleHandler.level = ALL
??!
This is Tomcat 9.0.98 on Linux with a stock conf/logging.properties file
(plus my .level=ALL for this filter)
What am I missing?
1. It may be that your web application has its own logging.properties
file in classp
t;>> java.util.logging.ConsoleHandler
> >>>
> >>> I shouldn't need the second line, since the default .handlers is
> >>> ConsoleHandler and the async handler for catalina.[date].
> >>>
> >>> I'm not seeing anything more detailed than I
I found a solution. It is not perfect but it works.
Man, I miss the old days of simple log4j-tomcat configurations.
Feel free to use, reproduce, modify (especially if you have
improvements) as you wish.
*Configuring Tomcat for log4j2 logging*
*NOTES*:
·A simpler configuration might be
ler and the async handler for catalina.[date].
I'm not seeing anything more detailed than INFO in catalina.out or
catalina.[date]. But...
1catalina.org.apache.juli.AsyncFileHandler.level = ALL
...
java.util.logging.ConsoleHandler.level = ALL
??!
This is Tomcat 9.0.98 on Linux with a sto
t seeing anything more detailed than INFO in catalina.out or
catalina.[date]. But...
1catalina.org.apache.juli.AsyncFileHandler.level = ALL
...
java.util.logging.ConsoleHandler.level = ALL
??!
This is Tomcat 9.0.98 on Linux with a stock conf/logging.properties file
(plus my .level=ALL for t
atalina.[date].
>
> I'm not seeing anything more detailed than INFO in catalina.out or
> catalina.[date]. But...
>
> 1catalina.org.apache.juli.AsyncFileHandler.level = ALL
> ...
> java.util.logging.ConsoleHandler.level = ALL
>
>
> ??!
>
> This is Tomcat 9.0.98 on Linux w
...
1catalina.org.apache.juli.AsyncFileHandler.level = ALL
...
java.util.logging.ConsoleHandler.level = ALL
??!
This is Tomcat 9.0.98 on Linux with a stock conf/logging.properties file
(plus my .level=ALL for this filter)
What am I missing?
-chris
-
Timothy,
On 3/12/25 1:00 PM, Timothy Resh wrote:
Thanks for your input on this issue. I have additional information on
this. What would happen if the temp directory gets this size of 38000
Files and 1.6GB of data? Has anyone seen tomcat slow down because of temp
directory size?
I don&#
Thanks for your input on this issue. I have additional information on
this. What would happen if the temp directory gets this size of 38000
Files and 1.6GB of data? Has anyone seen tomcat slow down because of temp
directory size?
On Sun, Mar 9, 2025 at 1:01 PM Suvendu Sekhar Mondal
wrote
ide[3]
[2] https://logging.apache.org/log4j/2.x/jakarta.html#replace-tomcat
Thanks for this. I have added this link to Tomcat's logging
documentation and it will be in the April release round.
Thanks!
If someone from the Tomcat team could review the "Integrating with
Jakarta EE&qu
Hi Bruno,
On 11.03.2025 15:50, Bruno Melloni wrote:
Thanks, excellent set of links and information!
* [2] is almost identical to what I "used to use" for Tomcat 8 and 10
log4j 2.x logging (the only real difference is the folder names I
chose). I am not sure when, but at
that can be updated and saved"
> factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
>pathname="conf/tomcat-users.xml" />
Debian utilizes ucf <https://manpages.debian.org/jessie/ucf/ucf.1.en.html>,
Update Configuration File, uti
1 - 100 of 1302 matches
Mail list logo
