Apache Tomcat 12+

2025-04-17 Thread William Crowell 
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://openjdk.org/jeps/8291976

What are the plans for the next major release of Tomcat?

Regards,

William Crowell


This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

Tomcat 9.0.104 Crashing at Startup on RHEL 8.4

2025-04-17 Thread RAY, DAVID 
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/apache/catalina/webresources/StandardRoot.getResource(
Ljava/lang/String;ZZ)Lorg/apache/catalina/WebResource;
Target=2_90_20190911_427071 (Linux 4.18.0-305.el8.ppc64le)
CPU=ppc64le (8 logical CPUs) (0x11c0e RAM)
--- Stack Backtrace ---
(0x7FFFB1950648 [libj9jit29.so+0x480648])
(0x7FFFB194E4A4 [libj9jit29.so+0x47e4a4])
(0x7FFFB21CE2AC [libj9jit29.so+0xcfe2ac])
(0x7FFFB1A1A058 [libj9jit29.so+0x54a058])
(0x7FFFB1A1B00C [libj9jit29.so+0x54b00c])
(0x7FFFB1A186D4 [libj9jit29.so+0x5486d4])
(0x7FFFB19E455C [libj9jit29.so+0x51455c])
(0x7FFFB1A0CAC0 [libj9jit29.so+0x53cac0])
(0x7FFFB1A06BD0 [libj9jit29.so+0x536bd0])
(0x7FFFB19E4224 [libj9jit29.so+0x514224])
(0x7FFFB19FB534 [libj9jit29.so+0x52b534])
(0x7FFFB21D0C8C [libj9jit29.so+0xd00c8c])
(0x7FFFB21BE714 [libj9jit29.so+0xcee714])
(0x7FFFB19F627C [libj9jit29.so+0x52627c])
(0x7FFFB21B947C [libj9jit29.so+0xce947c])
(0x7FFFB19EFE08 [libj9jit29.so+0x51fe08])
(0x7FFFB23BB4AC [libj9jit29.so+0xeeb4ac])
(0x7FFFB23B9284 [libj9jit29.so+0xee9284])
(0x7FFFB1F12FC0 [libj9jit29.so+0xa42fc0])
(0x7FFFB18BF1E8 [libj9jit29.so+0x3ef1e8])
(0x7FFFB18BCF68 [libj9jit29.so+0x3ecf68])
(0x7FFFB3CDE608 [libj9prt29.so+0x5e608])
(0x7FFFB18B4CB4 [libj9jit29.so+0x3e4cb4])
(0x7FFFB18B4124 [libj9jit29.so+0x3e4124])
(0x7FFFB18B257C [libj9jit29.so+0x3e257c])
(0x7FFFB18B2378 [libj9jit29.so+0x3e2378])
(0x7FFFB3CDE608 [libj9prt29.so+0x5e608])
(0x7FFFB18AFAA4 [libj9jit29.so+0x3dfaa4])
(0x7FFFB8119934 [libj9thr29.so+0x9934])
(0x7FFFB8EA87C8 [libpthread.so.0+0x87c8])
clone+0x74 (0x7FFFB8D401B8 [libc.so.6+0x1301b8])
---



Method_being_compiled=org/apache/catalina/webresources/Cache.getResource(Ljava/l
ang/String;Z)Lorg/apache/catalina/WebResource;
Target=2_90_20190911_427071 (Linux 4.18.0-305.el8.ppc64le)
CPU=ppc64le (8 logical CPUs) (0x11c0e RAM)
--- Stack Backtrace ---
(0x7FFFB1950648 [libj9jit29.so+0x480648])
(0x7FFFB194E4A4 [libj9jit29.so+0x47e4a4])
(0x7FFFB21CE2AC [libj9jit29.so+0xcfe2ac])
(0x7FFFB1A1A058 [libj9jit29.so+0x54a058])
(0x7FFFB1A1B00C [libj9jit29.so+0x54b00c])
(0x7FFFB1A186D4 [libj9jit29.so+0x5486d4])
(0x7FFFB19E455C [libj9jit29.so+0x51455c])
(0x7FFFB1A0CAC0 [libj9jit29.so+0x53cac0])
(0x7FFFB1A06BD0 [libj9jit29.so+0x536bd0])
(0x7FFFB19E4224 [libj9jit29.so+0x514224])
(0x7FFFB19FB534 [libj9jit29.so+0x52b534])
(0x7FFFB21D0C8C [libj9jit29.so+0xd00c8c])
(0x7FFFB21BE714 [libj9jit29.so+0xcee714])
(0x7FFFB19F627C [libj9jit29.so+0x52627c])
(0x7FFFB21B947C [libj9jit29.so+0xce947c])
(0x7FFFB19EFE08 [libj9jit29.so+0x51fe08])
(0x7FFFB23BB4AC [libj9jit29.so+0xeeb4ac])
(0x7FFFB23B9284 [libj9jit29.so+0xee9284])
(0x7FFFB1F12FC0 [libj9jit29.so+0xa42fc0])
(0x7FFFB18BF1E8 [libj9jit29.so+0x3ef1e8])
(0x7FFFB18BCF68 [libj9jit29.so+0x3ecf68])
(0x7FFFB3CDE608 [libj9prt29.so+0x5e608])
(0x7FFFB18B4CB4 [libj9jit29.so+0x3e4cb4])
(0x7FFFB18B4124 [libj9jit29.so+0x3e4124])
(0x7FFFB18B257C [libj9jit29.so+0x3e257c])
(0x7FFFB18B2378 [libj9jit29.so+0x3e2378])
(0x7FFFB3CDE608 [libj9prt29.so+0x5e608])
(0x7FFFB18AFAA4 [libj9jit29.so+0x3dfaa4])
(0x7FFFB8119934 [libj9thr29.so+0x9934])
(0x7FFFB8EA87C8 [libpthread.so.0+0x87c8])
clone+0x74 (0x7FFFB8D401B8 [libc.so.6+0x1301b8])

Thanks,
David Ray
Tarrant County College

Re: Tomcat 9.0.104 Crashing at Startup on RHEL 8.4

2025-04-17 Thread Mark Thomas 

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 appreciated:


That looks a JVM bug. One for your JVM vendor / RedHat depending on 
where you got it from.


No obvious changes on the Tomcat side that might have triggered the bug.

Mark






Method_being_compiled=org/apache/catalina/webresources/StandardRoot.getResource(
Ljava/lang/String;ZZ)Lorg/apache/catalina/WebResource;
Target=2_90_20190911_427071 (Linux 4.18.0-305.el8.ppc64le)
CPU=ppc64le (8 logical CPUs) (0x11c0e RAM)
--- Stack Backtrace ---
(0x7FFFB1950648 [libj9jit29.so+0x480648])
(0x7FFFB194E4A4 [libj9jit29.so+0x47e4a4])
(0x7FFFB21CE2AC [libj9jit29.so+0xcfe2ac])
(0x7FFFB1A1A058 [libj9jit29.so+0x54a058])
(0x7FFFB1A1B00C [libj9jit29.so+0x54b00c])
(0x7FFFB1A186D4 [libj9jit29.so+0x5486d4])
(0x7FFFB19E455C [libj9jit29.so+0x51455c])
(0x7FFFB1A0CAC0 [libj9jit29.so+0x53cac0])
(0x7FFFB1A06BD0 [libj9jit29.so+0x536bd0])
(0x7FFFB19E4224 [libj9jit29.so+0x514224])
(0x7FFFB19FB534 [libj9jit29.so+0x52b534])
(0x7FFFB21D0C8C [libj9jit29.so+0xd00c8c])
(0x7FFFB21BE714 [libj9jit29.so+0xcee714])
(0x7FFFB19F627C [libj9jit29.so+0x52627c])
(0x7FFFB21B947C [libj9jit29.so+0xce947c])
(0x7FFFB19EFE08 [libj9jit29.so+0x51fe08])
(0x7FFFB23BB4AC [libj9jit29.so+0xeeb4ac])
(0x7FFFB23B9284 [libj9jit29.so+0xee9284])
(0x7FFFB1F12FC0 [libj9jit29.so+0xa42fc0])
(0x7FFFB18BF1E8 [libj9jit29.so+0x3ef1e8])
(0x7FFFB18BCF68 [libj9jit29.so+0x3ecf68])
(0x7FFFB3CDE608 [libj9prt29.so+0x5e608])
(0x7FFFB18B4CB4 [libj9jit29.so+0x3e4cb4])
(0x7FFFB18B4124 [libj9jit29.so+0x3e4124])
(0x7FFFB18B257C [libj9jit29.so+0x3e257c])
(0x7FFFB18B2378 [libj9jit29.so+0x3e2378])
(0x7FFFB3CDE608 [libj9prt29.so+0x5e608])
(0x7FFFB18AFAA4 [libj9jit29.so+0x3dfaa4])
(0x7FFFB8119934 [libj9thr29.so+0x9934])
(0x7FFFB8EA87C8 [libpthread.so.0+0x87c8])
clone+0x74 (0x7FFFB8D401B8 [libc.so.6+0x1301b8])
---



Method_being_compiled=org/apache/catalina/webresources/Cache.getResource(Ljava/l
ang/String;Z)Lorg/apache/catalina/WebResource;
Target=2_90_20190911_427071 (Linux 4.18.0-305.el8.ppc64le)
CPU=ppc64le (8 logical CPUs) (0x11c0e RAM)
--- Stack Backtrace ---
(0x7FFFB1950648 [libj9jit29.so+0x480648])
(0x7FFFB194E4A4 [libj9jit29.so+0x47e4a4])
(0x7FFFB21CE2AC [libj9jit29.so+0xcfe2ac])
(0x7FFFB1A1A058 [libj9jit29.so+0x54a058])
(0x7FFFB1A1B00C [libj9jit29.so+0x54b00c])
(0x7FFFB1A186D4 [libj9jit29.so+0x5486d4])
(0x7FFFB19E455C [libj9jit29.so+0x51455c])
(0x7FFFB1A0CAC0 [libj9jit29.so+0x53cac0])
(0x7FFFB1A06BD0 [libj9jit29.so+0x536bd0])
(0x7FFFB19E4224 [libj9jit29.so+0x514224])
(0x7FFFB19FB534 [libj9jit29.so+0x52b534])
(0x7FFFB21D0C8C [libj9jit29.so+0xd00c8c])
(0x7FFFB21BE714 [libj9jit29.so+0xcee714])
(0x7FFFB19F627C [libj9jit29.so+0x52627c])
(0x7FFFB21B947C [libj9jit29.so+0xce947c])
(0x7FFFB19EFE08 [libj9jit29.so+0x51fe08])
(0x7FFFB23BB4AC [libj9jit29.so+0xeeb4ac])
(0x7FFFB23B9284 [libj9jit29.so+0xee9284])
(0x7FFFB1F12FC0 [libj9jit29.so+0xa42fc0])
(0x7FFFB18BF1E8 [libj9jit29.so+0x3ef1e8])
(0x7FFFB18BCF68 [libj9jit29.so+0x3ecf68])
(0x7FFFB3CDE608 [libj9prt29.so+0x5e608])
(0x7FFFB18B4CB4 [libj9jit29.so+0x3e4cb4])
(0x7FFFB18B4124 [libj9jit29.so+0x3e4124])
(0x7FFFB18B257C [libj9jit29.so+0x3e257c])
(0x7FFFB18B2378 [libj9jit29.so+0x3e2378])
(0x7FFFB3CDE608 [libj9prt29.so+0x5e608])
(0x7FFFB18AFAA4 [libj9jit29.so+0x3dfaa4])
(0x7FFFB8119934 [libj9thr29.so+0x9934])
(0x7FFFB8EA87C8 [libpthread.so.0+0x87c8])
clone+0x74 (0x7FFFB8D401B8 [libc.so.6+0x1301b8])

Thanks,
David Ray
Tarrant County College






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

RE: Tomcat 9.0.104 Crashing at Startup on RHEL 8.4

2025-04-17 Thread RAY, DAVID 

-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 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:

That looks a JVM bug. One for your JVM vendor / RedHat depending on where you 
got it from.

No obvious changes on the Tomcat side that might have triggered the bug.

Mark


> 
> 
> 
> Method_being_compiled=org/apache/catalina/webresources/StandardRoot.ge
> tResource( Ljava/lang/String;ZZ)Lorg/apache/catalina/WebResource;
> Target=2_90_20190911_427071 (Linux 4.18.0-305.el8.ppc64le) CPU=ppc64le 
> (8 logical CPUs) (0x11c0e RAM)
> --- Stack Backtrace ---
> (0x7FFFB1950648 [libj9jit29.so+0x480648])
> (0x7FFFB194E4A4 [libj9jit29.so+0x47e4a4]) (0x7FFFB21CE2AC 
> [libj9jit29.so+0xcfe2ac])
> (0x7FFFB1A1A058 [libj9jit29.so+0x54a058]) (0x7FFFB1A1B00C 
> [libj9jit29.so+0x54b00c])
> (0x7FFFB1A186D4 [libj9jit29.so+0x5486d4]) (0x7FFFB19E455C 
> [libj9jit29.so+0x51455c])
> (0x7FFFB1A0CAC0 [libj9jit29.so+0x53cac0])
> (0x7FFFB1A06BD0 [libj9jit29.so+0x536bd0])
> (0x7FFFB19E4224 [libj9jit29.so+0x514224])
> (0x7FFFB19FB534 [libj9jit29.so+0x52b534]) (0x7FFFB21D0C8C 
> [libj9jit29.so+0xd00c8c])
> (0x7FFFB21BE714 [libj9jit29.so+0xcee714]) (0x7FFFB19F627C 
> [libj9jit29.so+0x52627c]) (0x7FFFB21B947C 
> [libj9jit29.so+0xce947c])
> (0x7FFFB19EFE08 [libj9jit29.so+0x51fe08]) (0x7FFFB23BB4AC 
> [libj9jit29.so+0xeeb4ac])
> (0x7FFFB23B9284 [libj9jit29.so+0xee9284])
> (0x7FFFB1F12FC0 [libj9jit29.so+0xa42fc0])
> (0x7FFFB18BF1E8 [libj9jit29.so+0x3ef1e8])
> (0x7FFFB18BCF68 [libj9jit29.so+0x3ecf68])
> (0x7FFFB3CDE608 [libj9prt29.so+0x5e608])
> (0x7FFFB18B4CB4 [libj9jit29.so+0x3e4cb4])
> (0x7FFFB18B4124 [libj9jit29.so+0x3e4124]) (0x7FFFB18B257C 
> [libj9jit29.so+0x3e257c])
> (0x7FFFB18B2378 [libj9jit29.so+0x3e2378])
> (0x7FFFB3CDE608 [libj9prt29.so+0x5e608])
> (0x7FFFB18AFAA4 [libj9jit29.so+0x3dfaa4])
> (0x7FFFB8119934 [libj9thr29.so+0x9934])
> (0x7FFFB8EA87C8 [libpthread.so.0+0x87c8])
> clone+0x74 (0x7FFFB8D401B8 [libc.so.6+0x1301b8])
> ---
> 
> 
> 
> Method_being_compiled=org/apache/catalina/webresources/Cache.getResour
> ce(Ljava/l ang/String;Z)Lorg/apache/catalina/WebResource;
> Target=2_90_20190911_427071 (Linux 4.18.0-305.el8.ppc64le) CPU=ppc64le 
> (8 logical CPUs) (0x11c0e RAM)
> --- Stack Backtrace ---
> (0x7FFFB1950648 [libj9jit29.so+0x480648])
> (0x7FFFB194E4A4 [libj9jit29.so+0x47e4a4]) (0x7FFFB21CE2AC 
> [libj9jit29.so+0xcfe2ac])
> (0x7FFFB1A1A058 [libj9jit29.so+0x54a058]) (0x7FFFB1A1B00C 
> [libj9jit29.so+0x54b00c])
> (0x7FFFB1A186D4 [libj9jit29.so+0x5486d4]) (0x7FFFB19E455C 
> [libj9jit29.so+0x51455c])
> (0x7FFFB1A0CAC0 [libj9jit29.so+0x53cac0])
> (0x7FFFB1A06BD0 [libj9jit29.so+0x536bd0])
> (0x7FFFB19E4224 [libj9jit29.so+0x514224])
> (0x7FFFB19FB534 [libj9jit29.so+0x52b534]) (0x7FFFB21D0C8C 
> [libj9jit29.so+0xd00c8c])
> (0x7FFFB21BE714 [libj9jit29.so+0xcee714]) (0x7FFFB19F627C 
> [libj9jit29.so+0x52627c]) (0x7FFFB21B947C 
> [libj9jit29.so+0xce947c])
> (0x7FFFB19EFE08 [libj9jit29.so+0x51fe08]) (0x7FFFB23BB4AC 
> [libj9jit29.so+0xeeb4ac])
> (0x7FFFB23B9284 [libj9jit29.so+0xee9284])
> (0x7FFFB1F12FC0 [libj9jit29.so+0xa42fc0])
> (0x7FFFB18BF1E8 [libj9jit29.so+0x3ef1e8])
> (0x7FFFB18BCF68 [libj9jit29.so+0x3ecf68])
> (0x7FFFB3CDE608 [libj9prt29.so+0x5e608])
> (0x7FFFB18B4CB4 [libj9jit29.so+0x3e4cb4])
> (0x7FFFB18B4124 [libj9jit29.so+0x3e4124]) (0x7FFFB18B257C 
> [libj9jit29.so+0x3e257c])
> (0x7FFFB18B2378 [libj9jit29.so+0x3e2378])
> (0x7FFFB3CDE608 [libj9prt29.so+0x5e608])
> (0x7FFFB18AFAA4 [libj9jit29.so+0x3dfaa4])
> (0x7FFFB8119934 [libj9thr29.so+0x9934])
> (0x7FFFB8EA87C8 [libpthread.so.0+0x87c8])
> clone+0x74 (0x7FFFB8D401B8 [libc.so.6+0x1301b8])
> 
> Thanks,
> David Ray
> Tarrant County College
> 
> 
> 


Okay, thank you Mark.

Thanks,
David Ray
Tarrant County College



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

Re: Apache Tomcat 12+

2025-04-17 Thread William Crowell 
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 12+
To expand on some of that:

On 17/04/2025 16:47, Rémy Maucherat wrote:
> On Thu, Apr 17, 2025 at 5:16 PM William Crowell
>  wrote:
>>
>> 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?
>
> No, it'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 QUIC.

It is a bit of a simplification but QUIC (and therefore HTTP/3)
essentially trades increased CPU usage at the client/server for better
tolerance of poor networks.

Tomcat is not normally directly internet facing. It is typically sat
behind some form of load-balancer and/or TLS termination and/or reverse
proxy. In those scenarios poor network conditions aren't an issue so
using QUIC is costs CPU power which is something folks - particularly
those with large installations - try to minimise. It makes more sense to
use HTTP/1.1 in those scenarios.

Hence there isn't much requirement for an HTTP/3 implementation in
Tomcat at the moment.

>> Does it have anything to do with JEP draft 8291976?
>>
>> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopenjdk.org%2Fjeps%2F8291976&data=05%7C02%7CWCrowell%40perforce.com%7C701993891ea74599a43408dd7dd581c9%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638805078152291991%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=bA%2FPVllQeKUzyufCYhqY%2F2TcC5g9ikGQNvALzdX%2F178%3D&reserved=0

Not really. Although if that JEP exposes some useful parts of JSSE and
UDP that allows a native Java QUIC implementation on the server side I
would at least be interested.

>> What are the plans for the next major release of Tomcat?

Work is already underway on Tomcat 12. The plan is to start milestone
releases when there are enough 12.0.x specific features to make releases
worthwhile.

Current changelog is here:
https://github.com/apache/tomcat/blob/main/webapps/docs/changelog.xml

You want to pay attention to which items are above and below the
"backport and removal" line in each section. Only the entries above the
line are 12.0.x specific.

I don't think there is enough there yet but if users feel differently, I
could be persuaded into a milestone release.

I am currently working on Jakarta 12 updates for Servlet, Pages, EL and
WebSocket. I suspect we'll be at a point where there is something worth
releasing in a month or two.

>
> The QUIC plans have been on and off.

True. Currently more off than on. If we were to implement today, it
would probably be with panama and a native QUIC stack.

HTH,

MARK


>
> Rémy
>
>> Regards,
>>
>> William Crowell
>>
>>
>> This e-mail may contain information that is privileged or confidential. If 
>> you are not the intended recipient, please delete the e-mail and any 
>> attachments and notify us immediately.
>>
>
> -
> 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



CAUTION: This email originated from outside of the organization. Do not click 
on links or open attachments unless you recognize the sender and know the 
content is safe.


This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

Re: Apache Tomcat 12+

2025-04-17 Thread Mark Thomas 

To expand on some of that:

On 17/04/2025 16:47, Rémy Maucherat wrote:

On Thu, Apr 17, 2025 at 5:16 PM William Crowell
 wrote:


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?


No, it'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 QUIC.

It is a bit of a simplification but QUIC (and therefore HTTP/3) 
essentially trades increased CPU usage at the client/server for better 
tolerance of poor networks.


Tomcat is not normally directly internet facing. It is typically sat 
behind some form of load-balancer and/or TLS termination and/or reverse 
proxy. In those scenarios poor network conditions aren't an issue so 
using QUIC is costs CPU power which is something folks - particularly 
those with large installations - try to minimise. It makes more sense to 
use HTTP/1.1 in those scenarios.


Hence there isn't much requirement for an HTTP/3 implementation in 
Tomcat at the moment.



Does it have anything to do with JEP draft 8291976?

https://openjdk.org/jeps/8291976


Not really. Although if that JEP exposes some useful parts of JSSE and 
UDP that allows a native Java QUIC implementation on the server side I 
would at least be interested.



What are the plans for the next major release of Tomcat?


Work is already underway on Tomcat 12. The plan is to start milestone 
releases when there are enough 12.0.x specific features to make releases 
worthwhile.


Current changelog is here:
https://github.com/apache/tomcat/blob/main/webapps/docs/changelog.xml

You want to pay attention to which items are above and below the 
"backport and removal" line in each section. Only the entries above the 
line are 12.0.x specific.


I don't think there is enough there yet but if users feel differently, I 
could be persuaded into a milestone release.


I am currently working on Jakarta 12 updates for Servlet, Pages, EL and 
WebSocket. I suspect we'll be at a point where there is something worth 
releasing in a month or two.




The QUIC plans have been on and off.


True. Currently more off than on. If we were to implement today, it 
would probably be with panama and a native QUIC stack.


HTH,

MARK




Rémy


Regards,

William Crowell


This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.



-
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

Re: Apache Tomcat 12+

2025-04-17 Thread Rémy Maucherat 
On Thu, Apr 17, 2025 at 5:16 PM William Crowell
 wrote:
>
> 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?

No, it'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?
>
> Does it have anything to do with JEP draft 8291976?
>
> https://openjdk.org/jeps/8291976
>
> What are the plans for the next major release of Tomcat?

The QUIC plans have been on and off.

Rémy

> Regards,
>
> William Crowell
>
>
> This e-mail may contain information that is privileged or confidential. If 
> you are not the intended recipient, please delete the e-mail and any 
> attachments and notify us immediately.
>

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

Re: Content type unknown after upgrading Tomcat 10.1.39 => 10.1.40

2025-04-17 Thread Mark Thomas 

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 served by Tomcat my browser 
(Firefox) now downloads a file instead of displaying the (generated) 
HTML page. With the network inspector I discovered that the content-type 
in the response is set to "content/unknown;charset=UTF-8". When 
reverting back to 10.1.39 everything works; the content-type in the 
response is (as expected) "text/html;charset=UTF-8".


In the changelog I haven't seen anything regarding this.

The configuration files used to start Tomcat are exactly the same in 
both scenarios, and the application isn't changed.


Can anyone explain what's happening?


That looks like the result of fixing this bug:
https://bz.apache.org/bugzilla/show_bug.cgi?id=69623

A little more digging suggests that MIME type is only set for a resource 
when it is served via the default servlet. I suspect that lookup needs 
to be moved so MIME type is also 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 that 
contains the fix once I have implemented what I think is the fix.


2. You provide the simplest possible web application that reproduces the 
issue and I use that to test.


Which approach works best for you?

Mark


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

Re: Content type unknown after upgrading Tomcat 10.1.39 => 10.1.40

2025-04-17 Thread Thorsten Heit 

Hi Mark,


That looks like the result of fixing this bug:
https://bz.apache.org/bugzilla/show_bug.cgi?id=69623

A little more digging suggests that MIME type is only set for a resource 
when it is served via the default servlet. I suspect that lookup needs 
to be moved so MIME type is also 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 that 
contains the fix once I have implemented what I think is the fix.


2. You provide the simplest possible web application that reproduces the 
issue and I use that to test.


Thanks for your answer. I see whether I can create a minimal reproducer.


Regards

Thorsten

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