Re: Tomcat 11, Java 21 and Windows 32-bit support

2023-06-20 Thread Mark Thomas
On 20/06/2023 23:34, Christopher Schultz wrote: Mark, On 6/15/23 05:31, Mark Thomas wrote: All, I'm currently looking at adding the Windows specific binary distributions to Maven Central as a result of PR #609 [1]. That got me thinking whether Windows 32-bit was still supported. Some quick

Re: Tomcat 11, Java 21 and Windows 32-bit support

2023-06-20 Thread Christopher Schultz
Mark, On 6/15/23 05:31, Mark Thomas wrote: All, I'm currently looking at adding the Windows specific binary distributions to Maven Central as a result of PR #609 [1]. That got me thinking whether Windows 32-bit was still supported. Some quick research found that: - The only currently suppo

[Bug 66660] StaticMember doesn't support lazy hostname resolution (useful in K8s)

2023-06-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=0 --- Comment #8 from romain.manni-bucau --- Facade your pods by services or just impl a custom.discovery but static one looks like a wrong usage for you and not willing to use k8s api will require another registration mechanism anyway -- You a

[tomcat] branch main updated: Further fix for regression in previous BZ 66574 fix.

2023-06-20 Thread markt
This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/main by this push: new 1403f0ee85 Further fix for regression in previous BZ

[tomcat] branch 8.5.x updated: Further fix for regression in previous BZ 66574 fix.

2023-06-20 Thread markt
This is an automated email from the ASF dual-hosted git repository. markt 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 70ccf2a624 Further fix for regression in previous B

[tomcat] branch 9.0.x updated: Further fix for regression in previous BZ 66574 fix.

2023-06-20 Thread markt
This is an automated email from the ASF dual-hosted git repository. markt 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 ac297f1ab8 Further fix for regression in previous B

[tomcat] branch 10.1.x updated: Further fix for regression in previous BZ 66574 fix.

2023-06-20 Thread markt
This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch 10.1.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/10.1.x by this push: new d72b0fe4c7 Further fix for regression in previous

[Bug 66660] StaticMember doesn't support lazy hostname resolution (useful in K8s)

2023-06-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=0 --- Comment #7 from Diego Rivera --- > Sure, but you're asking for a dynamic static membership list here, basically. Kind of, but not. The only thing "dynamic" is the IP address to which each hostname would resolve to. If the hostname string

[Bug 66660] StaticMember doesn't support lazy hostname resolution (useful in K8s)

2023-06-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=0 --- Comment #6 from Remy Maucherat --- (In reply to Diego Rivera from comment #4) > (In reply to Mark Thomas from comment #2) > > It looks like it needs more Javadoc and some documentation but I suspect > > using the k8s specific membership pro

[Bug 66660] StaticMember doesn't support lazy hostname resolution (useful in K8s)

2023-06-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=0 --- Comment #5 from Diego Rivera --- To clarify: the problem is that MemberImpl expects the target member to exist or be resolvable at object construction. If that resolution fails, then it pukes out and the member is then discarded by the over

[Bug 66660] StaticMember doesn't support lazy hostname resolution (useful in K8s)

2023-06-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=0 --- Comment #4 from Diego Rivera --- (In reply to Mark Thomas from comment #2) > It looks like it needs more Javadoc and some documentation but I suspect > using the k8s specific membership provider would be a better solution: > > https://tomc

[Bug 66660] StaticMember doesn't support lazy hostname resolution (useful in K8s)

2023-06-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=0 --- Comment #3 from Diego Rivera --- (In reply to romain.manni-bucau from comment #1) > Hi, probably not yet mainstream but did you evaluated to use a custom DNS > resolver impl delegating to the JVM when the host values were not known to > be

[Bug 66660] StaticMember doesn't support lazy hostname resolution (useful in K8s)

2023-06-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=0 --- Comment #2 from Mark Thomas --- It looks like it needs more Javadoc and some documentation but I suspect using the k8s specific membership provider would be a better solution: https://tomcat.apache.org/tomcat-9.0-doc/api/org/apache/catalin

[Bug 66660] StaticMember doesn't support lazy hostname resolution (useful in K8s)

2023-06-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=0 --- Comment #1 from romain.manni-bucau --- Hi, probably not yet mainstream but did you evaluated to use a custom DNS resolver impl delegating to the JVM when the host values were not known to be the pod ones? (https://bugs.openjdk.org/browse/JD

[Bug 66660] New: StaticMember doesn't support lazy hostname resolution (useful in K8s)

2023-06-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=0 Bug ID: 0 Summary: StaticMember doesn't support lazy hostname resolution (useful in K8s) Product: Tomcat 9 Version: 9.0.x Hardware: All OS: All

Re: Signature expiration on security.txt

2023-06-20 Thread Mark Thomas
On 20/06/2023 18:09, Christopher Schultz wrote: All, I just discovered that our security.txt file[1] had passed its "expiration date" and just updated it and re-signed it. Is there any existing process for "checking things" where we could insert a check for "is security.txt about to expire"

Signature expiration on security.txt

2023-06-20 Thread Christopher Schultz
All, I just discovered that our security.txt file[1] had passed its "expiration date" and just updated it and re-signed it. Is there any existing process for "checking things" where we could insert a check for "is security.txt about to expire" into that workflow? Would ASF's monitoring syst

svn commit: r1910521 - /tomcat/site/trunk/docs/.well-known/security.txt

2023-06-20 Thread schultz
Author: schultz Date: Tue Jun 20 17:03:16 2023 New Revision: 1910521 URL: http://svn.apache.org/viewvc?rev=1910521&view=rev Log: Update security.txt with a new expiration date. Modified: tomcat/site/trunk/docs/.well-known/security.txt Modified: tomcat/site/trunk/docs/.well-known/security.txt

[tomcat] 01/03: Fix IDE warning

2023-06-20 Thread markt
This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/tomcat.git commit ab801f8a4f44b6baa5c5b13b80a43946e8ba738a Author: Mark Thomas AuthorDate: Tue Jun 20 10:18:29 2023 +0100 Fix IDE warnin

[tomcat] 02/03: Update WebSocket API to align with latest proposals

2023-06-20 Thread markt
This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/tomcat.git commit 46578dc3e7cc98ca907a2711ca48ecfc07042b9b Author: Mark Thomas AuthorDate: Tue Jun 20 10:19:10 2023 +0100 Update WebSock

[tomcat] branch main updated (e0320d4894 -> 1b1685b377)

2023-06-20 Thread markt
This is an automated email from the ASF dual-hosted git repository. markt pushed a change to branch main in repository https://gitbox.apache.org/repos/asf/tomcat.git from e0320d4894 Remove unnecessary test. new ab801f8a4f Fix IDE warning new 46578dc3e7 Update WebSocket API to align

[tomcat] 03/03: Add getSession() to SendResult

2023-06-20 Thread markt
This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/tomcat.git commit 1b1685b377f547bbece829dfcbf7f93d56624274 Author: Mark Thomas AuthorDate: Tue Jun 20 13:46:31 2023 +0100 Add getSession

[Bug 66659] New: Tomcat does not send FIN message upon request by client to close TCP connection

2023-06-20 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66659 Bug ID: 66659 Summary: Tomcat does not send FIN message upon request by client to close TCP connection Product: Tomcat 10 Version: 10.1.8 Hardware: PC Status: