You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by William Crowell <WC...@perforce.com.INVALID> on 2025/04/17 15:15:40 UTC

Apache Tomcat 12+

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.


Re: Apache Tomcat 12+

Posted by Christopher Schultz <ch...@christopherschultz.net>.
Rémy,

On 4/17/25 11:47 AM, Rémy Maucherat wrote:
> On Thu, Apr 17, 2025 at 5:16 PM William Crowell
> <WC...@perforce.com.invalid> 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.

A bit off topic, but this is my favorite thing from the 
recently-released Java 24: https://openjdk.org/jeps/491

JEP 491: Synchronize Virtual Threads without Pinning

This JEP makes using Virtual Threads practical for most web 
applications. Support for Virtual Threads was added in previous Tomcat 
versions (that is, earlier than Tomcat 12), but the nature of VTs in the 
JVM has kind of made them a bit of a flop since there is so much 
synchronized code out there in the world.

Having Java 24 remove pinning of those threads means that every JDBC 
driver is no longer a boat-anchor on every web application that uses 
those drivers, and the promise of "simpler code that performs well" that 
Virtual Threads was meant to deliver is actually, well, deliverable.

-chris


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


Re: Apache Tomcat 12+

Posted by William Crowell <WC...@perforce.com.INVALID>.
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 <ma...@apache.org>
Date: Thursday, April 17, 2025 at 1:30 PM
To: users@tomcat.apache.org <us...@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
> <WC...@perforce.com.invalid> 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<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-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@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+

Posted by Mark Thomas <ma...@apache.org>.
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
> <WC...@perforce.com.invalid> 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-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 


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


Re: Apache Tomcat 12+

Posted by Rémy Maucherat <re...@apache.org>.
On Thu, Apr 17, 2025 at 5:16 PM William Crowell
<WC...@perforce.com.invalid> 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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org