Re: isGraalAvailable error

[Blake McBride]

I should add that in the stack trace I am seeing:

loadClass:862 GroovyClassLoader (groovy.lang)
loadClass:973 GroovyClassLoader (groovy.lang)
loadClass:960 GroovyClassLoader(groovy.lang)
loadClass:593, GroovyClassLoader$InnerLoader (groovy.lang)

Thanks!

Blake


On Fri, Jun 9, 2023 at 7:40 PM Blake McBride  wrote:

> Greetings,
>
> I am running a tomcat app as follows:
>
> Java 17
> Tomcat 9.0.65
>
> This is a program that used to run under Java 8, but now I'm getting some
> sort of error finding isGrallAvailable.  The error looks as follows:
>
> isGrallAvailable:114, JreCompat (org.apache.tomcat.util.compat)
>
> Sure appreciate any help.
>
> Thanks!
>
> Blake McBride
>
>

isGraalAvailable error

[Blake McBride]

Greetings,

I am running a tomcat app as follows:

Java 17
Tomcat 9.0.65

This is a program that used to run under Java 8, but now I'm getting some
sort of error finding isGrallAvailable.  The error looks as follows:

isGrallAvailable:114, JreCompat (org.apache.tomcat.util.compat)

Sure appreciate any help.

Thanks!

Blake McBride

Setting security response headers when Valve returns error..

[Amit Pande]

Hello,

Wanted some inputs on setting HSTS (or other response headers) when returning 
error from a valve.

The server.xml has the valve "org.apache.catalina.valves.RemoteAddrValve" 
configured with a deny status of HTTP 404.

Also, the Tomcat's web.xml has 
"org.apache.catalina.filters.HttpHeaderSecurityFilter" confugred.

The requirement is to set the security related headers even when the request is 
denied from the  "org.apache.catalina.valves.RemoteAddrValve", which I don't 
see being set.

What is the right way to address such requirement?

Did I miss anything here?

Thanks,
Amit

Re: Tomcat 11 Release Date

[Rémy Maucherat]

On Fri, Jun 9, 2023 at 10:38 AM Mark Thomas  wrote:
>
> On 08/06/2023 21:37, William Crowell wrote:
> > Mark,
> >
> > Thank you for your reply.  Any ideas on Tomcat 11 features that will be 
> > included with a final release next year?
>
> Virtual thread support was the the first major new feature and that was
> included in the recent 11.0.0-M7 release. There will probably be more
> loom related changes as it starts being used and bottlenecks are discovered.
>
> We hoped to take advantage of project Panama to simplify OpenSSL
> integration but that looks like it will remain in preview for Java 21.
>
> QUIC is still on the radar but without Panama support it looks unlikely
> that we'll add QUIC support to Tomcat 11.

First item would be: Panama is non preview in Java 22. I really hope so !
Following this, it should become possible to compile with 22 and
target 21 (except for the classes actually using Panama).

Rémy

> The Jakarta spec changes look to be mostly about clarifying grey areas
> and small feature improvements.
>
> Other than that, the best thing to do is follow the change log and if
> there are features you'd like to see, speak up.
>
> Mark#
>
>
> >
> > Regards,
> >
> > William Crowell
> >
> > From: Mark Thomas 
> > Date: Thursday, June 8, 2023 at 4:05 PM
> > To: users@tomcat.apache.org 
> > Subject: Re: Tomcat 11 Release Date
> > On 08/06/2023 19:56, William Crowell wrote:
> >> Good afternoon,
> >>
> >> I know we are in milestone 7 of Apache Tomcat 11, but do any of you know 
> >> when the release date will be for Apache Tomcat 11? It does not have to be 
> >> an exact date, but just a ballpark date.
> >
> > The criteria for a stable release are:
> > - All implemented Jakarta specifications are released
> > - Tomcat has fully implemented all the specifications
> > - Committer judgement
> >
> > Expanding on those, my best guess for the Jakarta EE specs to be
> > released is March. Tomcat follows the Jakarta development pretty closely
> > so I am fairly confident that Tomcat will have fully implemented the
> > relevant Jakarta EE 11 APIs long before the specs are finally released.
> >
> > The committer judgement has changed over the years. Back when the major
> > Tomcat versions had significantly different code bases, we wanted to
> > allow time for bugs to be found before declaring a major release stable.
> > Currently we try and keep the code bases more in-line and are actively
> > looking for opportunities to reduce differences where we can. The major
> > benefit of this is a greater degree of confidence in the code. My best
> > guess in that the committers will declare Tomcat 11 stable a few Tomcat
> > release cycles after the Jakarta EE 11 release.
> >
> > All that adds up to somewhere around June 2024 as a best guess at the
> > moment.
> >
> > HTH,
> >
> > Mark
> >
> > -
> > 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.
> >
> >
>
> -
> 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: Tomcat 11 Release Date

[William Crowell]

Mark,

Thank you sir and will let you know on additional features.  Have a great 
weekend.

Regards,


Bill Crowell | Enterprise Architect, 
OpenLogic
Perforce 
Software
P: +1 720 536 0699
Visit us on: 
LinkedIn
 | 
Twitter
 | 
Facebook
 | 
YouTube


From: Mark Thomas 
Date: Friday, June 9, 2023 at 4:36 AM
To: users@tomcat.apache.org 
Subject: Re: Tomcat 11 Release Date
On 08/06/2023 21:37, William Crowell wrote:
> Mark,
>
> Thank you for your reply.  Any ideas on Tomcat 11 features that will be 
> included with a final release next year?

Virtual thread support was the the first major new feature and that was
included in the recent 11.0.0-M7 release. There will probably be more
loom related changes as it starts being used and bottlenecks are discovered.

We hoped to take advantage of project Panama to simplify OpenSSL
integration but that looks like it will remain in preview for Java 21.

QUIC is still on the radar but without Panama support it looks unlikely
that we'll add QUIC support to Tomcat 11.

The Jakarta spec changes look to be mostly about clarifying grey areas
and small feature improvements.

Other than that, the best thing to do is follow the change log and if
there are features you'd like to see, speak up.

Mark#


>
> Regards,
>
> William Crowell
>
> From: Mark Thomas 
> Date: Thursday, June 8, 2023 at 4:05 PM
> To: users@tomcat.apache.org 
> Subject: Re: Tomcat 11 Release Date
> On 08/06/2023 19:56, William Crowell wrote:
>> Good afternoon,
>>
>> I know we are in milestone 7 of Apache Tomcat 11, but do any of you know 
>> when the release date will be for Apache Tomcat 11? It does not have to be 
>> an exact date, but just a ballpark date.
>
> The criteria for a stable release are:
> - All implemented Jakarta specifications are released
> - Tomcat has fully implemented all the specifications
> - Committer judgement
>
> Expanding on those, my best guess for the Jakarta EE specs to be
> released is March. Tomcat follows the Jakarta development pretty closely
> so I am fairly confident that Tomcat will have fully implemented the
> relevant Jakarta EE 11 APIs long before the specs are finally released.
>
> The committer judgement has changed over the years. Back when the major
> Tomcat versions had significantly different code bases, we wanted to
> allow time for bugs to be found before declaring a major release stable.
> Currently we try and keep the code bases more in-line and are actively
> looking for opportunities to reduce differences where we can. The major
> benefit of this is a greater degree of confidence in the code. My best
> guess in that the committers will declare Tomcat 11 stable a few Tomcat
> release cycles after the Jakarta EE 11 release.
>
> All that adds up to somewhere around June 2024 as a best guess at the
> moment.
>
> HTH,
>
> Mark
>
> -
> 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.
>
>

-
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: Tomcat 11 Release Date

[Mark Thomas]

On 08/06/2023 21:37, William Crowell wrote:

Mark,

Thank you for your reply.  Any ideas on Tomcat 11 features that will be 
included with a final release next year?


Virtual thread support was the the first major new feature and that was 
included in the recent 11.0.0-M7 release. There will probably be more 
loom related changes as it starts being used and bottlenecks are discovered.


We hoped to take advantage of project Panama to simplify OpenSSL 
integration but that looks like it will remain in preview for Java 21.


QUIC is still on the radar but without Panama support it looks unlikely 
that we'll add QUIC support to Tomcat 11.


The Jakarta spec changes look to be mostly about clarifying grey areas 
and small feature improvements.


Other than that, the best thing to do is follow the change log and if 
there are features you'd like to see, speak up.


Mark#




Regards,

William Crowell

From: Mark Thomas 
Date: Thursday, June 8, 2023 at 4:05 PM
To: users@tomcat.apache.org 
Subject: Re: Tomcat 11 Release Date
On 08/06/2023 19:56, William Crowell wrote:

Good afternoon,

I know we are in milestone 7 of Apache Tomcat 11, but do any of you know when 
the release date will be for Apache Tomcat 11? It does not have to be an exact 
date, but just a ballpark date.


The criteria for a stable release are:
- All implemented Jakarta specifications are released
- Tomcat has fully implemented all the specifications
- Committer judgement

Expanding on those, my best guess for the Jakarta EE specs to be
released is March. Tomcat follows the Jakarta development pretty closely
so I am fairly confident that Tomcat will have fully implemented the
relevant Jakarta EE 11 APIs long before the specs are finally released.

The committer judgement has changed over the years. Back when the major
Tomcat versions had significantly different code bases, we wanted to
allow time for bugs to be found before declaring a major release stable.
Currently we try and keep the code bases more in-line and are actively
looking for opportunities to reduce differences where we can. The major
benefit of this is a greater degree of confidence in the code. My best
guess in that the committers will declare Tomcat 11 stable a few Tomcat
release cycles after the Jakarta EE 11 release.

All that adds up to somewhere around June 2024 as a best guess at the
moment.

HTH,

Mark

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




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

Re: [ANN] Apache Tomcat 9.0.76 available

[Mark Thomas]

On 09/06/2023 09:16, Greg Huber wrote:
Thanksthe apache-tomcat-9.0.76.tar.gz link is not working though. 
Zip is OK.


Looks like some sort of CDN snafu. It may resolve itself if it is cache 
related. Meanwhile, the file is available via the archives link.


Mark



On 09/06/2023 08:51, Rémy Maucherat wrote:

The Apache Tomcat team announces the immediate availability of Apache
Tomcat 9.0.76.

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.76 is a bugfix and feature release. The notable
changes compared to 9.0.75 include:

- Add support for virtual threads. (Java 21+ only)

- Update HTTP/2 to use the RFC-9218 prioritization scheme.

- Deprecate the xssProtectionEnabled from HttpHeaderSecurityFilter
    and set the default value to false.

- Update Tomcat Native to 2.0.4 which includes binaries for Windows
    built with OpenSSL 3.0.9.

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



-
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: [ANN] Apache Tomcat 9.0.76 available

[Greg Huber]

Thanksthe apache-tomcat-9.0.76.tar.gz link is not working though.  
Zip is OK.


On 09/06/2023 08:51, Rémy Maucherat wrote:

The Apache Tomcat team announces the immediate availability of Apache
Tomcat 9.0.76.

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.76 is a bugfix and feature release. The notable
changes compared to 9.0.75 include:

- Add support for virtual threads. (Java 21+ only)

- Update HTTP/2 to use the RFC-9218 prioritization scheme.

- Deprecate the xssProtectionEnabled from HttpHeaderSecurityFilter
and set the default value to false.

- Update Tomcat Native to 2.0.4 which includes binaries for Windows
built with OpenSSL 3.0.9.

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



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

[ANN] Apache Tomcat 9.0.76 available

[Rémy Maucherat]

The Apache Tomcat team announces the immediate availability of Apache
Tomcat 9.0.76.

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.76 is a bugfix and feature release. The notable
changes compared to 9.0.75 include:

- Add support for virtual threads. (Java 21+ only)

- Update HTTP/2 to use the RFC-9218 prioritization scheme.

- Deprecate the xssProtectionEnabled from HttpHeaderSecurityFilter
   and set the default value to false.

- Update Tomcat Native to 2.0.4 which includes binaries for Windows
   built with OpenSSL 3.0.9.

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: Apache Tomcat 9.x end of life

[Osipov, Michael (SMD IT IN)]

On 2023-06-08 18:17, Mark Thomas wrote:

On 08/06/2023 16:32, Zoltan Balogh wrote:

Dear Apache Team,

I just would like to ask is there any planned EOL for Tomcat 9?


Best guess at the moment (and it is only a guess - no decisions have 
been made) is 3 years after 8.5.x is EOL which gives a date of 31 March 
2027.


It is worth noting that Tomcat major versions track releases of the 
Jakarta Servlet specification and there has been an effort from the 
Jakarta project to increase the release cadence. Delays are also not 
unheard of. The estimate above could easily be a year out in either 
direction.


We are heavily using Java 8 that is supported until 2030, so we expect 
Apache Tomcat 9 will be also support while Java 8 is supported.


That is extremely unlikely at this point.

Important note that Tomcat 9 is the last release that works fine with 
Java 8 along with Java EE. Therefore, it is highly important for us to 
have a maintained Tomcat 9 for Java 8.


Once Tomcat 9.0.x reaches EOL we will provide, assuming there is demand, 
Tomcat 9.10.x which will be Tomcat 10.1.x but with the Java EE 8 API. 
The minimum Java requirement for 9.10.x will be Java 11.


Once Tomcat 10.1.x reaches EOL we will provide Tomcat 9.11.x which would 
be Tomcat 11.0.x but with the Java EE 8 API.


I wonder to what extent this is necessary at all. Baseline is Java EE 8 
and Java 8 and it should stay that way, I guess. If some code is back 
ported, sure it needs to be refitted to Java 8 if necessary, otherwise 
there would no more Java EE 8 capable container on Java 8. Moving to a 
new Java version is one thing, but replacing namespaces is a completely 
different one for people.


M

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

Re: AbstractEndpoint#logCertificate() prints incorrect information

[Osipov, Michael (SMD IT IN)]

On 2023-06-08 15:36, Mark Thomas wrote:

On 08/06/2023 14:22, Osipov, Michael (SMD IT IN) wrote:

On 2023-06-08 14:45, Mark Thomas wrote:

On 08/06/2023 12:25, Osipov, Michael (SMD IT IN) wrote:

Folks,

I am running of 8.5.88 and noticed these lines in my catalina.out:
2023-06-08T12:38:54.938 INFORMATION [main] 
org.apache.tomcat.util.net.AbstractEndpoint.logCertificate 
Connector [https-openssl-apr-8444], TLS virtual host 
[deblndw024v.ad001.siemens.net], certificate type [RSA] configured 
from [/net/home/smartld/.keystore] using alias [tomcat] and with 
trust store [null]
2023-06-08T12:38:55.036 INFORMATION [main] 
org.apache.tomcat.util.net.AbstractEndpoint.logCertificate 
Connector [https-openssl-apr-18444], TLS virtual host 
[deblndw024v.ad001.siemens.net], certificate type [RSA] configured 
from [/net/home/smartld/.keystore] using alias [tomcat] and with 
trust store [/opt/openssl/certs]


I have two connectors configured (both APR and OpenSSL), the only 
difference is that the second one (18444) requires TLS client 
certificates:
keepAliveTimeout="30" maxParameterCount="1000"

  maxHttpHeaderSize="24576" maxThreads="250"
  SSLEnabled="true" scheme="https" secure="true"
  defaultSSLHostConfigName="deblndw024v.ad001.siemens.net">
  protocols="TLSv1.2+TLSv1.3"

    honorCipherOrder="true" disableSessionTickets="true"
ciphers="HIGH:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!3DES:!MD5:!PSK:!DSS:!SHA1:!SHA256:!SHA384">
    certificateFile="/opt/openssl/deblndw024v.ad001.siemens.net/cert.crt"

certificateKeyFile="/opt/openssl/deblndw024v.ad001.siemens.net/key.crt"
  certificateKeyPassword="..." type="RSA" />
  



and

keepAliveTimeout="720" maxParameterCount="1000"

  maxHttpHeaderSize="24576" maxThreads="250"
  SSLEnabled="true" scheme="https" secure="true"
  defaultSSLHostConfigName="deblndw024v.ad001.siemens.net">
  protocols="TLSv1.2+TLSv1.3"

    honorCipherOrder="true" disableSessionTickets="true"
    certificateVerification="optional" 
certificateVerificationDepth="5"

    caCertificatePath="/opt/openssl/certs"
ciphers="HIGH:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!3DES:!MD5:!PSK:!DSS:!SHA1:!SHA256:!SHA384">
    certificateFile="/opt/openssl/deblndw024v.ad001.siemens.net/cert.crt"

certificateKeyFile="/opt/openssl/deblndw024v.ad001.siemens.net/key.crt"
  certificateKeyPassword="..." type="RSA" />
    
  value="/opt/openssl/siemens-medium+strong-clientcert-cacerts.crt" />

    
  



The information displayed is partially wrong. It missed to 
differentiate between store types 
(org.apache.tomcat.util.net.SSLHostConfigCertificate.StoreType).


I disagree with the characterization that the data is wrong. There 
are many TLS configuration attributes. A few are displayed, most are 
not. StoreType is one of those that is not.


The aim isn't to display the full configuration (admins can look at 
server.xml for that). The intention is to make clear, for each 
configured server certificate, which configuration files are being 
used. The idea being that you can then examine the relevant files 
and/or server.xml if there is an issue.


I'm not seeing much of a case for adding StoreType.


..and that's the problem. Neither [/net/home/smartld/.keystore] nor 
[tomcat] is used because I have never configured it. I don't expect 
full display, but correct display. I rather see no information than 
incorrect information. I don't insist on printing the storeType at 
all, it needs to be used in Java code to determine what configuration 
has to be printed.


Got it. Yep - open a bug report for that.


Done: https://bz.apache.org/bugzilla/show_bug.cgi?id=66635


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

RE: Apache Tomcat 9.x end of life

[Zoltan Balogh]

Great, and thanks a lot for sharing this information.

I totally agreee with you that involving the community in this discussion is 
very useful to see the demands.

Kind Regards,

Zoltan Balogh


-Original Message-
From: Mark Thomas  
Sent: Thursday, June 8, 2023 6:18 PM
To: users@tomcat.apache.org
Subject: Re: Apache Tomcat 9.x end of life

On 08/06/2023 16:32, Zoltan Balogh wrote:
> Dear Apache Team,
> 
> I just would like to ask is there any planned EOL for Tomcat 9?

Best guess at the moment (and it is only a guess - no decisions have been made) 
is 3 years after 8.5.x is EOL which gives a date of 31 March 2027.

It is worth noting that Tomcat major versions track releases of the Jakarta 
Servlet specification and there has been an effort from the Jakarta project to 
increase the release cadence. Delays are also not unheard of. The estimate 
above could easily be a year out in either direction.

> We are heavily using Java 8 that is supported until 2030, so we expect Apache 
> Tomcat 9 will be also support while Java 8 is supported.

That is extremely unlikely at this point.

> Important note that Tomcat 9 is the last release that works fine with Java 8 
> along with Java EE. Therefore, it is highly important for us to have a 
> maintained Tomcat 9 for Java 8.

Once Tomcat 9.0.x reaches EOL we will provide, assuming there is demand, Tomcat 
9.10.x which will be Tomcat 10.1.x but with the Java EE 8 API. 
The minimum Java requirement for 9.10.x will be Java 11.

Once Tomcat 10.1.x reaches EOL we will provide Tomcat 9.11.x which would be 
Tomcat 11.0.x but with the Java EE 8 API.

And so on.

All our planning to date has assumed that the primary demand would be for the 
newer features (that require newer JREs) supported by newer Tomcat versions but 
with the Java EE 8 API. If that assumption is incorrect and the primary demand 
is for Tomcat 9.0.x that runs on Java 8 then it is possible that we could just 
keep supporting Tomcat 9.0.x. 
Given that Tomcat 9.0.x will run quite happily on any currently supported 
version of Java (and should continue to do so) the EOL for Java 8 isn't really 
relevant to when we stop supporting Tomcat 9.0.x.

Any change in our plans for ongoing 9.0.x support would need some discussion. 
Input from the community would be especially useful.

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