Re: [VOTE] Release Apache Tomcat 10.1.0-M16
On Thu, Jun 2, 2022 at 3:22 PM Mark Thomas wrote: > > The proposed Apache Tomcat 10.1.0-M16 release is now available for > voting. For all previous branches, the "M" was dropped as soon as the spec was final (and its implementation was complete too ;) ). Maybe this is better though, all regular numbered releases would be either stable or skipped, while the "M" would be alpha or beta. Rémy > I am proposing this as a beta release since the Jakarta EE APIs are now > finalised and Tomcat's implementation of the API changes is complete. > > Applications that run on Tomcat 9 and earlier will not run on Tomcat 10 > without changes. Java EE applications designed for Tomcat 9 and earlier > may be placed in the $CATALINA_BASE/webapps-javaee directory and Tomcat > will automatically convert them to Jakarta EE and copy them to the > webapps directory. > > The notable changes compared to 10.1.0-M15 are: > > - Refactor synchronization blocks locking on SocketWrapper to use >ReentrantLock to support users wishing to experiment with project >Loom. > > - Correct a regression in the support added for encrypted PKCS#1 >formatted private keys in the previous release that broke support >for unencrypted PKCS#1 formatted private keys. > > - Increase the default buffer size for cluster messages from 43800 >to 65536 bytes. This is expected to improve performance for large >messages when running on Linux based systems. > > For full details, see the change log: > https://nightlies.apache.org/tomcat/tomcat-10.1.x/docs/changelog.html > > It can be obtained from: > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-10/v10.1.0-M16/ > > The Maven staging repo is: > https://repository.apache.org/content/repositories/orgapachetomcat-1376 > > The tag is: > https://github.com/apache/tomcat/tree/10.1.0-M16 > 02c4004b52be88a04a7372577d56da0f9ed3a7fe > > > The proposed 10.1.0-M16 release is: > [ ] Broken - do not release > [ ] Beta - go ahead and release as 10.1.0-M16 (beta) > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 10.1.0-M16
On 03/06/2022 09:14, Rémy Maucherat wrote: On Thu, Jun 2, 2022 at 3:22 PM Mark Thomas wrote: The proposed Apache Tomcat 10.1.0-M16 release is now available for voting. For all previous branches, the "M" was dropped as soon as the spec was final (and its implementation was complete too ;) ). Thanks for the reminder. I'd forgotten that. Maybe this is better though, all regular numbered releases would be either stable or skipped, while the "M" would be alpha or beta. Other projects would probably switch to RC now. I don't think that really works for us because of the frequency of releases and the way we do them. Essentially every stable release is an RC and we just move to the next version if we find an issue. I do wonder if the "M" designation will put people off testing it. On the other hand, the code is pretty stable since all 4 versions are fairly close these days. Hmm. I'll leave this one as M and I'm leaning towards your suggestion of continuing to use M until we are happy to call it stable. I think we are a little way from a stable release at the moment. I'd like to get Tomcat Native 2.0.x released and have all that working, go through the remaining items in TOMCAT-NEXT.txt and then have a few releases without issues first. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 10.1.0-M16
On Thu, Jun 2, 2022 at 3:22 PM Mark Thomas wrote: > > The proposed Apache Tomcat 10.1.0-M16 release is now available for > voting. > > I am proposing this as a beta release since the Jakarta EE APIs are now > finalised and Tomcat's implementation of the API changes is complete. > > Applications that run on Tomcat 9 and earlier will not run on Tomcat 10 > without changes. Java EE applications designed for Tomcat 9 and earlier > may be placed in the $CATALINA_BASE/webapps-javaee directory and Tomcat > will automatically convert them to Jakarta EE and copy them to the > webapps directory. > > The notable changes compared to 10.1.0-M15 are: > > - Refactor synchronization blocks locking on SocketWrapper to use >ReentrantLock to support users wishing to experiment with project >Loom. > > - Correct a regression in the support added for encrypted PKCS#1 >formatted private keys in the previous release that broke support >for unencrypted PKCS#1 formatted private keys. > > - Increase the default buffer size for cluster messages from 43800 >to 65536 bytes. This is expected to improve performance for large >messages when running on Linux based systems. > > For full details, see the change log: > https://nightlies.apache.org/tomcat/tomcat-10.1.x/docs/changelog.html > > It can be obtained from: > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-10/v10.1.0-M16/ > > The Maven staging repo is: > https://repository.apache.org/content/repositories/orgapachetomcat-1376 > > The tag is: > https://github.com/apache/tomcat/tree/10.1.0-M16 > 02c4004b52be88a04a7372577d56da0f9ed3a7fe > > > The proposed 10.1.0-M16 release is: > [ ] Broken - do not release > [X] Beta - go ahead and release as 10.1.0-M16 (beta) Let's start the beta cycle then ! Rémy - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 10.0.22
On Thu, Jun 2, 2022 at 7:11 PM Mark Thomas wrote: > > The proposed Apache Tomcat 10.0.22 release is now available for > voting. > > Apache Tomcat 10.0.x implements Jakarta EE 9 and, as such, the primary > package for all the specification APIs has changed from javax.* to jakarta.* > > Applications that run on Tomcat 9 will not run on Tomcat 10 without > changes. Java EE applications designed for Tomcat 9 and earlier may be > placed in the $CATALINA_BASE/webapps-javaee directory and Tomcat will > automatically convert them to Jakarta EE and copy them to the webapps > directory > > The notable changes compared to 10.0.21 are: > > - Correct a regression in the support added for encrypted PKCS#1 >formatted private keys in the previous release that broke support >for unencrypted PKCS#1 formatted private keys. > > - Increase the default buffer size for cluster messages from 43800 >to 65536 bytes. This is expected to improve performance for large >messages when running on Linux based systems. > > - When using TLS with non-blocking writes and the NIO connector, >ensure that flushing the buffers attempts to empty all of the >output buffers. > > Along with lots of other bug fixes and improvements. > > For full details, see the changelog: > https://nightlies.apache.org/tomcat/tomcat-10.0.x/docs/changelog.html > > It can be obtained from: > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-10/v10.0.22/ > > The Maven staging repo is: > https://repository.apache.org/content/repositories/orgapachetomcat-1377 > > The tag is: > https://github.com/apache/tomcat/tree/10.0.22 > babca1854c6f7068069d501e7f6b9cca13943056 > > The proposed 10.0.22 release is: > [ ] Broken - do not release > [X] Stable - go ahead and release as 10.0.21 (stable) Rémy - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 9.0.64
On Thu, Jun 2, 2022 at 9:46 PM Rémy Maucherat wrote: > > The proposed Apache Tomcat 9.0.64 release is now available for voting. > > The notable changes compared to 9.0.63 are: > > - Correct a regression in the support added for encrypted PKCS#1 >formatted private keys in the previous release that broke support >for unencrypted PKCS#1 formatted private keys. > > - Increase the default buffer size for cluster messages from 43800 >to 65536 bytes. This is expected to improve performance for large >messages when running on Linux based systems. > > - When using TLS with non-blocking writes and the NIO connector, >ensure that flushing the buffers attempts to empty all of the >output buffers. > > Along with lots of other bug fixes and improvements. > > For full details, see the changelog: > https://nightlies.apache.org/tomcat/tomcat-9.0.x/docs/changelog.html > > It can be obtained from: > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.64/ > The Maven staging repo is: > https://repository.apache.org/content/repositories/orgapachetomcat-1378 > The tag is: > https://github.com/apache/tomcat/tree/9.0.64 > 1419d61f200be876baddb0997919fb82c230a857 > > The proposed 9.0.64 release is: > [ ] Broken - do not release > [X] Stable - go ahead and release as 9.0.64 (stable) Rémy - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [VOTE] Release Apache Tomcat 9.0.64
[X] Stable - go ahead and release as 9.0.64 (stable) Rémy Maucherat 于2022年6月3日周五 03:46写道： > The proposed Apache Tomcat 9.0.64 release is now available for voting. > > The notable changes compared to 9.0.63 are: > > - Correct a regression in the support added for encrypted PKCS#1 >formatted private keys in the previous release that broke support >for unencrypted PKCS#1 formatted private keys. > > - Increase the default buffer size for cluster messages from 43800 >to 65536 bytes. This is expected to improve performance for large >messages when running on Linux based systems. > > - When using TLS with non-blocking writes and the NIO connector, >ensure that flushing the buffers attempts to empty all of the >output buffers. > > Along with lots of other bug fixes and improvements. > > For full details, see the changelog: > https://nightlies.apache.org/tomcat/tomcat-9.0.x/docs/changelog.html > > It can be obtained from: > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.64/ > The Maven staging repo is: > https://repository.apache.org/content/repositories/orgapachetomcat-1378 > The tag is: > https://github.com/apache/tomcat/tree/9.0.64 > 1419d61f200be876baddb0997919fb82c230a857 > > The proposed 9.0.64 release is: > [ ] Broken - do not release > [ ] Stable - go ahead and release as 9.0.64 (stable) > > Rémy > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
Re: [VOTE] Release Apache Tomcat 10.0.22
[X] Stable - go ahead and release as 10.0.21 (stable) Mark Thomas 于2022年6月3日周五 01:11写道： > The proposed Apache Tomcat 10.0.22 release is now available for > voting. > > Apache Tomcat 10.0.x implements Jakarta EE 9 and, as such, the primary > package for all the specification APIs has changed from javax.* to > jakarta.* > > Applications that run on Tomcat 9 will not run on Tomcat 10 without > changes. Java EE applications designed for Tomcat 9 and earlier may be > placed in the $CATALINA_BASE/webapps-javaee directory and Tomcat will > automatically convert them to Jakarta EE and copy them to the webapps > directory > > The notable changes compared to 10.0.21 are: > > - Correct a regression in the support added for encrypted PKCS#1 >formatted private keys in the previous release that broke support >for unencrypted PKCS#1 formatted private keys. > > - Increase the default buffer size for cluster messages from 43800 >to 65536 bytes. This is expected to improve performance for large >messages when running on Linux based systems. > > - When using TLS with non-blocking writes and the NIO connector, >ensure that flushing the buffers attempts to empty all of the >output buffers. > > Along with lots of other bug fixes and improvements. > > For full details, see the changelog: > https://nightlies.apache.org/tomcat/tomcat-10.0.x/docs/changelog.html > > It can be obtained from: > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-10/v10.0.22/ > > The Maven staging repo is: > https://repository.apache.org/content/repositories/orgapachetomcat-1377 > > The tag is: > https://github.com/apache/tomcat/tree/10.0.22 > babca1854c6f7068069d501e7f6b9cca13943056 > > The proposed 10.0.22 release is: > [ ] Broken - do not release > [ ] Stable - go ahead and release as 10.0.21 (stable) > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
[Bug 66103] New: MemoryRealm documentation needs to be reference file watching support
https://bz.apache.org/bugzilla/show_bug.cgi?id=66103
Bug ID: 66103
Summary: MemoryRealm documentation needs to be reference file
watching support
Product: Tomcat 8
Version: 8.5.79
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: Documentation
Assignee: dev@tomcat.apache.org
Reporter: mw...@loftware.com
Target Milestone:
The Memory Realm documentation specifies "When Tomcat first starts up, it loads
all defined users and their associated information from the users file. Changes
to the data in this file will not be recognized until Tomcat is restarted."
This is no longer true (see bug 58590). By default, the Memory Realm now does
use a background process to monitor changes to the tomcat-users.xml file. The
documentation should be updated with this information, and also should mention
the boolean parameter that is used to turn this off ("watchSource").
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 66103] MemoryRealm documentation needs to be reference file watching support
https://bz.apache.org/bugzilla/show_bug.cgi?id=66103 Remy Maucherat changed: What|Removed |Added Resolution|--- |INVALID Status|NEW |RESOLVED OS||All --- Comment #1 from Remy Maucherat --- The MemoryRealm still does not support reloading. However, the user database based on a file does. Not the same realm. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
