Apache Tomcat 10 and Jakarta EE 9 - an update

Hi all, There has been a fair amount of progress made both towards a Tomcat 10 release and Jakarta EE 9 since my State of the Cat talk at ApacheCon EU in October. For those of you that haven't seen it is is on YouTube: https://www.youtube.com/watch?v=hfgO6R9o5Tw In order to update the Tomcat comm

[Bug 55477] Add a solution to map a realm name to a security role

https://bz.apache.org/bugzilla/show_bug.cgi?id=55477 --- Comment #20 from Christopher Schultz --- (In reply to Michael Osipov from comment #19) > (In reply to Christopher Schultz from comment #18) > > How applicable is in web.xml, here? > > As far as I know, this is per-servlet which can be ver

[Bug 64082] Nio2Endpoint for async request doesn't clear OutputBuffer when socket has already been closed (response mixup)

https://bz.apache.org/bugzilla/show_bug.cgi?id=64082 --- Comment #7 from Christopher Schultz --- (In reply to william.crowell from comment #4) > Setting org.apache.catalina.connector.RECYCLE_FACADES to true did work. Excellent. Since it "works", are you also able to reliably reproduce the error

Re: [tomcat] branch 9.0.x updated: Add new connector attribute to control facade recycling

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Rémy, On 1/23/20 4:28 AM, r...@apache.org wrote: > This is an automated email from the ASF dual-hosted git > repository. > > remm pushed a commit to branch 9.0.x in repository > https://gitbox.apache.org/repos/asf/tomcat.git > > > The following c

Re: [tomcat] branch 9.0.x updated: Add new connector attribute to control facade recycling

On Fri, Jan 24, 2020 at 8:11 PM Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Rémy, > > On 1/23/20 4:28 AM, r...@apache.org wrote: > > This is an automated email from the ASF dual-hosted git > > repository. > > > > remm pushed a

[tomcat] branch 9.0.x updated: Restore constant to avoid unwanted API change

This is an automated email from the ASF dual-hosted git repository. remm pushed a commit to branch 9.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/9.0.x by this push: new 39b8baf Restore constant to avoid unwanted API chan

[tomcat] branch 8.5.x updated: Restore constant to avoid unwanted API change

This is an automated email from the ASF dual-hosted git repository. remm pushed a commit to branch 8.5.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/8.5.x by this push: new a08ad79 Restore constant to avoid unwanted API chan

[tomcat] branch 7.0.x updated: Restore constant to avoid unwanted API change

This is an automated email from the ASF dual-hosted git repository. remm pushed a commit to branch 7.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/7.0.x by this push: new 0eaefa3 Restore constant to avoid unwanted API chan

[Bug 64082] Nio2Endpoint for async request doesn't clear OutputBuffer when socket has already been closed (response mixup)

https://bz.apache.org/bugzilla/show_bug.cgi?id=64082 --- Comment #8 from william.crow...@roguewave.com --- > Are you also able to reliably reproduce the error without RECYCLE_FACADES > enabled? Yes, it happens on each test run. > Tomcat (usually) properly protects these objects from shared-use,

[Bug 64082] Nio2Endpoint for async request doesn't clear OutputBuffer when socket has already been closed (response mixup)

https://bz.apache.org/bugzilla/show_bug.cgi?id=64082 --- Comment #9 from Christopher Schultz --- (In reply to william.crowell from comment #8) > > Are you also able to reliably reproduce the error without RECYCLE_FACADES > > enabled? > > Yes, it happens on each test run. Great. > > Tomcat (us