Am 22.05.24 um 19:21 schrieb Mark Thomas:
All,
I've been looking at the WebDav Servlet for the last few days and in
particular how it interacts with Microsoft clients.
Basic operations including:
- directory listings
- create new file
- create new directory
- rename
- update contents (ie
Am 09.05.24 um 20:12 schrieb Christopher Schultz:
The proposed Apache Tomcat 10.1.24 release is now available for
voting.
The notable changes compared to 10.1.23 are:
- Correct error handling for asynchronous requests
- Refactor HTTP header parsing to use common parsing code and fix
Am 03.05.24 um 22:37 schrieb Rémy Maucherat:
The proposed Apache Tomcat 9.0.89 release is now available for voting.
The notable changes compared to 9.0.88 are:
- Refactor HTTP header parsing to use common parsing code and fix
non-blocking reads of chunked request bodies including trailer
Am 03.05.24 um 18:22 schrieb Mark Thomas:
The proposed Apache Tomcat 11.0.0-M20 release is now available for
voting.
Apache Tomcat 11.0.0-M20 is a milestone release of the 11.0.x branch and
has been made to provide users with early access to the new features in
Apache Tomcat 11.0.x so that
Am 21.04.24 um 17:15 schrieb Rémy Maucherat:
On Sun, Apr 21, 2024 at 11:52 AM Rainer Jung wrote:
Am 16.04.24 um 15:11 schrieb Christopher Schultz:
The proposed Apache Tomcat 10.1.23 release is now available for
voting. Apache Tomcat 10.1.21 was canceled due to a release-build
mistake
Am 16.04.24 um 15:11 schrieb Christopher Schultz:
The proposed Apache Tomcat 10.1.23 release is now available for
voting. Apache Tomcat 10.1.21 was canceled due to a release-build
mistake and Apache Tomcat 10.1.22 was cancelled due to an option in
startup scripts which would have caused Java
Am 18.04.24 um 09:08 schrieb bugzi...@apache.org:
https://bz.apache.org/bugzilla/show_bug.cgi?id=68910
--- Comment #3 from Michael Osipov ---
(In reply to Christopher Schultz from comment #1)
(In reply to Michael Osipov from comment #0)
since we also do support LibreSSL [...]
Note: Support
Hi Konstantin,
Am 17.04.24 um 21:44 schrieb Konstantin Kolinko:
ср, 17 апр. 2024 г. в 17:21, Rainer Jung :
Am 17.04.24 um 15:34 schrieb Michael Osipov:
Rainer, I do not fully understand the problem here. We use libtool to solve
exactly this problem with versioned SONAMEs. It will create
Am 17.04.24 um 22:46 schrieb Michael Osipov:
On 2024/04/17 14:21:06 Rainer Jung wrote:
Am 17.04.24 um 15:34 schrieb Michael Osipov:
Rainer, I do not fully understand the problem here. We use libtool to solve
exactly this problem with versioned SONAMEs. It will create symlinks to the
SONAME
Am 17.04.24 um 15:34 schrieb Michael Osipov:
Rainer, I do not fully understand the problem here. We use libtool to solve
exactly this problem with versioned SONAMEs. It will create symlinks to the
SONAME.
Do you expect anyone even with dlopen() to load libfoo.o.{SOVERSION} unless it
is
Hi there,
I did some small tests using OpenSSL/Panama with TC 10.1.23 for running
the unit tests.
First: they seem to work well using JDK 22 with OpenSSL 3.0.13, 3.1.5,
3.2.1 and 3.3.0. For JDK 23 the tests are still running, but also look
good up to now.
But some things around native
Am 09.04.24 um 15:13 schrieb Rémy Maucherat:
The proposed Apache Tomcat 11.0.0-M19 release is now available for
voting.
Apache Tomcat 11.0.0-M19 is a milestone release of the 11.0.x branch and
has been made to provide users with early access to the new features in
Apache Tomcat 11.0.x so that
Thanks Rémy. Things happen, at least we found it before it hit the street.
Am 11.04.24 um 20:52 schrieb Rémy Maucherat:
On Thu, Apr 11, 2024 at 7:21 PM Rainer Jung wrote:
Hi Rémy,
I think this breaks 10.1 on Java 11, since --enable-native-access was
introduced later.
I was certain I
Am 10.04.24 um 20:51 schrieb Christopher Schultz:
The proposed Apache Tomcat 10.1.22 release is now available for
voting. Apache Tomcat 10.1.21 was canceled due to a release-build
mistake. There are no source-level changes between 10.1.21 and 10.1.22.
The notable changes compared to 10.1.20
Hi Rémy,
I think this breaks 10.1 on Java 11, since --enable-native-access was
introduced later.
Best regards,
Rainer
Am 22.03.24 um 14:13 schrieb r...@apache.org:
This is an automated email from the ASF dual-hosted git repository.
remm pushed a commit to branch 10.1.x
in repository
You need to look in the published (built) BUILDING.txt file, not the raw
sources. The raw sources are meant to prouce a build, the yre not for
human consumption.
You can e.g. download a published form og Tomcat 8.5.100 and look into
BUILDING.txt there.
Regards,
Rainer
Am 22.03.24 um 13:01
Am 20.03.24 um 18:50 schrieb Romain Manni-Bucau:
Le mer. 20 mars 2024 à 18:43, Rainer Jung a
écrit :
Am 20.03.24 um 18:34 schrieb Romain Manni-Bucau:
Hi Chris,
Thread dumps being dump of threads - literally os threads - and virtual
threads not being threads at all - they are runnables
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>
Le mer. 20 mars 2024 à 18:20, Christopher Schultz <
ch...@christopherschultz.net> a écrit :
Rainer,
Thanks for writing this up.
On 3/20/24 07:22, Rainer
Am 20.03.24 um 18:17 schrieb Christopher Schultz:
Rainer,
Thanks for writing this up.
On 3/20/24 07:22, Rainer Jung wrote:
I wanted to share an observation and I hope the things are correct how
I am describing them. Maybe things have already improved and I am not
aware of it, hints welcome
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>
Le me
Hi hi,
I wanted to share an observation and I hope the things are correct how I
am describing them. Maybe things have already improved and I am not
aware of it, hints welcome.
Part of JEP 425 (Project Loom, Java virtual threads) discusses how to
handle observability of virtual threads from
Thanks again, I will keep an eye on it.
Am 15.03.24 um 20:43 schrieb Mark Thomas:
On 08/03/2024 20:28, Rainer Jung wrote:
Again, this is not a new failure and it happens extremely infrequent.
Observed with JSSE on various Linux distributions and with various JVM
versions and vendors. Only
Again, this is not a new failure and it happens extremely infrequent.
Observed with JSSE on various Linux distributions and with various JVM
versions and vendors. Only observed for TC 8.5 and 9, but for 10.1 and
11 the unit tests are run with much fewer JVM combinations so I can not
exclude
Am 07.03.24 um 21:51 schrieb Rainer Jung:
Am 07.03.24 um 18:50 schrieb Mark Thomas:
On 07/03/2024 11:20, Rainer Jung wrote:
As always thanks a lot for the investigation and forthcoming fix. Let
me know when I can help!
I've committed a fix that worked for me locally but I was focring
Am 07.03.24 um 18:50 schrieb Mark Thomas:
On 07/03/2024 11:20, Rainer Jung wrote:
As always thanks a lot for the investigation and forthcoming fix. Let
me know when I can help!
I've committed a fix that worked for me locally but I was focring the
test failure via the debugger. I'm fairly
As always thanks a lot for the investigation and forthcoming fix. Let me
know when I can help!
Am 07.03.24 um 16:55 schrieb Mark Thomas:
On 02/03/2024 05:58, Rainer Jung wrote:
Hi there,
for a long time I get sporadic failures in
org.apache.coyote.http2.TestRfc9218. It happens for all
Hi there,
for a long time I get sporadic failures in
org.apache.coyote.http2.TestRfc9218. It happens for all branches of TC,
for NIO and NIO2 and with JSSE and tcnative. Tested platforms Linux and
Solaris see this. And JVM versions 1.8.0, 11, 17 and 21 show it. It is
also not restricted to a
Thank you Remy for fixing it and the explanation.
Am 27.02.24 um 15:33 schrieb Rémy Maucherat:
On Tue, Feb 27, 2024 at 1:32 PM Rainer Jung wrote:
Hi Mark, hi all,
coming back to this: the reason, why you could not reproduce is, that I
explicitly set
test.sslImplementation
s null
inside isClientRenegotiationSupported.
Best regards,
Rainer
Am 18.01.24 um 21:48 schrieb Mark Thomas:
On 18/01/2024 12:33, Rainer Jung wrote:
Hi all,
after the refactorings for the testing of the forbidden client
initiated renegotiations, these unit tests fail for me for the last
OK, great and sorry I didn't notice the fix!
Am 17.02.24 um 17:18 schrieb Mark Thomas:
On 16/02/2024 23:50, Rainer Jung wrote:
Hi there,
I see sporadic NullPointerExceptions when running the new unit test in
org.apache.tomcat.websocket.TestWsSessionSuspendResume:
Yep. My bad. The fix
Hi there,
I see sporadic NullPointerExceptions when running the new unit test in
org.apache.tomcat.websocket.TestWsSessionSuspendResume:
Testcase: testSuspendThenClose took 1.952 sec
Caused an ERROR
Cannot invoke "org.apache.tomcat.websocket.WsSession.isClosed()" because
Hi all,
after the refactorings for the testing of the forbidden client initiated
renegotiations, these unit tests fail for me for the last tags of TC 8.5
and 9, but not for 10.1 and 11. I am using JSSE and the tests fail
consistently for all four JDK vendors I am testing against on all linux
Am 03.01.24 um 12:29 schrieb ma...@apache.org:
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 9c5f303e9aea86564c15ed83491d9a4b6beff829
Author: Mark Thomas
AuthorDate:
Am 03.01.24 um 12:29 schrieb ma...@apache.org:
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 8fe3db67fdd69c160367982e85b23bfe01689c5c
Author: Mark Thomas
AuthorDate:
Am 08.12.23 um 15:04 schrieb Rémy Maucherat:
On Fri, Dec 8, 2023 at 3:01 PM Rainer Jung wrote:
Hi Remy,
I tried to build TC 11 with Java 22, but cuirrenttly it fails with
errors like:
[javac]
.../java/org/apache/tomcat/util/openssl/openssl_h_Macros.java:469:
error: MemorySegment
Hi Remy,
I tried to build TC 11 with Java 22, but cuirrenttly it fails with
errors like:
[javac]
.../java/org/apache/tomcat/util/openssl/openssl_h_Macros.java:469:
error: MemorySegment is a preview API and is disabled by default.
[javac] public static void
I just noticed the skip.build.java.version part, sorry for the noise.
Am 11.11.23 um 01:42 schrieb Rainer Jung:
It seems we can now only run TC 10.1 unit tests using Java 17?
I'd like to also run them with Java versions for which TC itself is
supported, so for TC 10.1 with Java 11
BZ 68117: Fix typo and escaping in libtool flag
introduced in 1.2.49.
ecd005d07 is described below
commit ecd005d0792441c4510dc4c2d9348979ab71ddcc
Author: Rainer Jung
AuthorDate: Fri Nov 10 11:38:04 2023 +0100
BZ 68117: Fix typo and escaping in libtool flag introduced in
1.2.49.
Do we
Hi there,
in BZ 67628 (OpenSSLCipherConfigurationParser#parse() produces
misleading false positive cipher warnings) the following question was
raised:
Am 03.11.23 um 09:30 schrieb bugzi...@apache.org:
https://bz.apache.org/bugzilla/show_bug.cgi?id=67628
--- Comment #9 from Mark Thomas ---
Should have gone to the list.
I think the mod_jk build process does not make it available online like
the Tomcat one does, but here's the current section:
Changes between 1.2.48 and 1.2.49
Apache
* Update: Retrieve default request id from mod_unique_id. It can also
be
I don't have a windows build setup for mod_jk at hand right now, but if
ou want more eyes to look at the error just post it. I am probably
responsible for it, because I changes quite a bit if code structure to
introduce the logging context.
Best regards,
Rainer
Am 05.09.23 um 13:18 schrieb Rainer Jung:
Am 05.09.23 um 12:50 schrieb Mark Thomas:
On 05/09/2023 11:40, Rainer Jung wrote:
I saw we use for older versions
in the changelog, but since the last version this is missing. Is this
an oversight, or did we change the style sheet? Should we
Am 05.09.23 um 12:50 schrieb Mark Thomas:
On 05/09/2023 11:40, Rainer Jung wrote:
I saw we use for older versions
in the changelog, but since the last version this is missing. Is this
an oversight, or did we change the style sheet? Should we have the
"subsection" everywhere
I saw we use for older versions
in the changelog, but since the last version this is missing. Is this an
oversight, or did we change the style sheet? Should we have the
"subsection" everywhere or remove everywhere? Any ideas?
Thanks and regards,
Rainer
Hi Han,
Am 24.08.23 um 04:31 schrieb Han Li:
On Aug 24, 2023, at 10:11, Rainer Jung wrote:
Am 24.08.23 um 01:31 schrieb Mark Thomas:
The proposed Apache Tomcat 8.5.93 release is now available for voting.
The notable changes compared to 8.5.92 are:
- If an application or library sets both
Am 24.08.23 um 01:31 schrieb Mark Thomas:
The proposed Apache Tomcat 8.5.93 release is now available for voting.
The notable changes compared to 8.5.92 are:
- If an application or library sets both a non-500 error code and the
jakarta.servlet.error.exception request attribute, use the
Hi Mark,
thanks for the tag. Do you intend to tag 1.2 as well?
Thanks and regards,
Rainer
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Am 10.07.23 um 20:15 schrieb Christopher Schultz:
All,
On 7/6/23 11:31, Christopher Schultz wrote:
The proposed Apache Tomcat 8.5.91 release is now available for voting.
The notable changes compared to 8.5.90 are:
- Add ContextNamingInfoListener, a listener which creates context naming
I already did the fix but forgot the changelog item, because otherwise
the changelog for the version would be empty ...
Am 04.07.23 um 12:00 schrieb Mark Thomas:
On 04/07/2023 10:45, Rainer Jung wrote:
I see, the checksum and the version number in the comment was updated,
but not the one used
I see, the checksum and the version number in the comment was updated,
but not the one used for the download:
diff --git a/build.properties.default b/build.properties.default
index 172a08a083..aa8179820c 100644
--- a/build.properties.default
+++ b/build.properties.default
@@ -318,10 +318,10 @@
Am 03.07.23 um 21:33 schrieb Mark Thomas:
The proposed Apache Tomcat 11.0.0-M8 release is now available for
voting.
Apache Tomcat 11.0.0-M8 is a milestone release of the 11.0.x branch and
has been made to provide users with early access to the new features in
Apache Tomcat 11.0.x so that they
Am 06.06.23 um 12:57 schrieb Mark Thomas:
On 05/06/2023 21:20, Rainer Jung wrote:
Something is wrong with our regeneration of configure in the release
process, at least for the 2.x branch (main). The configure script
contains "LT_INIT" verbatim instead of LT_INIT being replaced by i
Am 08.06.23 um 05:50 schrieb Rainer Jung:
The new TestKeyHeader fails for me very frequently for TC 9 and TC 8.5,
but not for 10.1 or 11.
For TC 9 it fails roughly 30-50% of the times I run it. It fails for
jsse and for tcnative and for a wide range of JDKs and RHEL/SLES Linux
versions
The new TestKeyHeader fails for me very frequently for TC 9 and TC 8.5,
but not for 10.1 or 11.
For TC 9 it fails roughly 30-50% of the times I run it. It fails for
jsse and for tcnative and for a wide range of JDKs and RHEL/SLES Linux
versions.
The failure happens only for NIO2, not for
Something is wrong with our regeneration of configure in the release
process, at least for the 2.x branch (main). The configure script
contains "LT_INIT" verbatim instead of LT_INIT being replaced by its
script implementation. I can't actually say what is wrong :(
If I run "autoreconf --force
Am 09.05.23 um 19:38 schrieb Christopher Schultz:
The proposed Apache Tomcat 8.5.89 release is now available for voting.
The notable changes compared to 8.5.88 are:
- Many improvements to the JSON access log valve.
- Deprecate support for the HTTP Connector settings rejectIllegalHeader
m whenever an incubator
module is resolved.
I guess we cań live with that.
Sorry for the noise,
Rainer
Am 04.05.23 um 12:40 schrieb Rainer Jung:
Hi there,
when testing TC 10.1 and 11 I get lots of
[junit] WARNING: Using incubator modules: jdk.incubator.foreign
lines in the output. This ha
Hi there,
when testing TC 10.1 and 11 I get lots of
[junit] WARNING: Using incubator modules: jdk.incubator.foreign
lines in the output. This happens when testing with Java 17. Not with 11
and not with 20 or 21. Don't know about 12-16 and 18-19.
We do have a block in build.xml that adds an
Hi all,
after I added some missing functionality to the JsonAccessLogValve I
added new tests for the AbstractAccessLogValve and JsonAccessLogValve.
The tests use access log valve classes derived from the two, which write
their output to a string. The tests check the log lines resulting from
Hi all,
I am looking at the new access log valve to add support for the pattern
fields with sub keys (headers, attributes etc.).
Many of those have free text values, so ensuring correct encodig is
important. I noticed, that the AbstractAccessLogValve already does
almost correct JSON
Hi Mark,
Am 08.03.23 um 20:15 schrieb ma...@apache.org:
...
diff --git a/test/org/apache/tomcat/websocket/TestWsWebSocketContainerSSL.java
b/test/org/apache/tomcat/websocket/TestWsWebSocketContainerSSL.java
new file mode 100644
index 00..eb44ac6aed
--- /dev/null
+++
Hi Mark,
only with Java 1.7.0 and TC 8.5 the new test throws an ERROR. It occurs
many times, all almost looking the same, here's an example:
16-Apr-2023 22:47:40.891 INFO [main]
org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case
[testDigestAuthentication[12:
Hi there,
I get a (not very important) unit test failure for all tags of this
month when running with
openjdk version "21-ea" 2023-09-19
OpenJDK Runtime Environment (build 21-ea+16-1326)
OpenJDK 64-Bit Server VM (build 21-ea+16-1326, mixed mode, sharing)
Test output is:
Testsuite:
Am 28.02.23 um 09:49 schrieb Mark Thomas:
On 28/02/2023 07:22, Rémy Maucherat wrote:
wrote:
On 2/27/23 16:09, Rémy Maucherat wrote:
On Mon, Feb 27, 2023 at 9:41 PM Mark Thomas wrote:
On 27/02/2023 20:36, schu...@apache.org wrote:
Have 'pre-release' indicate the the release is
I think the test certs in test/org/apache/tomcat/util/net just expired.
At least I start to get failures with
Caused by: java.security.cert.CertificateExpiredException: NotAfter: Fri
Feb 17 15:28:35 CET 2023
and the files in git are two years old.
Best regards,
Rainer
Am 10.02.23 um 22:04 schrieb Christopher Schultz:
Rainer,
On 2/10/23 15:08, Rainer Jung wrote:
Am 10.02.23 um 17:05 schrieb Christopher Schultz:
Mark,
I'm having trouble building on MacOS Ventura.
I downloaded the source tarball file from
https://dist.apache.org/repos/dist/dev/tomcat
Am 10.02.23 um 17:05 schrieb Christopher Schultz:
Mark,
I'm having trouble building on MacOS Ventura.
I downloaded the source tarball file from
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-connectors/native/2.0.3/source/tomcat-native-2.0.3-src.tar.gz, untarred it, and then ran the
APR 1.7.1 will be replaced by 1.7.2, because in 1.7.1 the tarball was
rolled with a directory containing an RC verion in its name.
So 1.7.2 will be the same source code as 1.7.1, but with a packaging
failure fixed.
The release is expected to happen either later today or tomorrow.
Best
It is probably not the most common combination, but when running TC
8.5.85 unit tests with Java 1.7.0 plus tcnative 2.0.2 build against
OpenSSL 3.1.0beta1, the test testPost() fails all 8 iterations it uses with:
javax.net.ssl.SSLException: ciphertext sanity check failed
at
Any plans to backport this for TC 9? JreCompat seems to provide
isJre16Available() for TC 9, so backport should work. I can confirm I
still see the failures for 9.0.71, but only for Java 17 and 21 (most of
the runs with Java 17 but not every run; Java 16 not tested, no failures
for 8 and 11).
This tag and the ones in the other branches can't be cleanly build from
scratch due to a inconsistency in build.properties.default. See details
in "Re: [tomcat] branch main updated: Update testing/validation
libraries". The fix is not complicated though.
Thanks and regards,
Rainer
Am
Hi Mark,
Am 06.01.23 um 16:25 schrieb ma...@apache.org:
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:
The tests testNonBlockingWriteError02NoSwallow() and
testNonBlockingWriteError02Swallow() of TestNonBlockingAPI fail for me
on Solaris 11. I am using Java 11 and TC 10.1.4 but it seems it is not
specific to these. The test loops unterminated doing flush on Solaris
until after 60 seconds the
I observe the following behavior for 10.1.4, but it might neither be a
regression nor version specific at all.
I am calling a JSP which writes a few bytes, then does
"Thread.sleep(2);" and then writes the remaining things.
When calling it with HTTP/1.1 it works for all connector types.
Thank you Mark!
Am 05.12.22 um 16:01 schrieb Mark Thomas:
Fixed.
The changes are in the current OpenSSL main development branch which
(currently) is configured to be 3.2.x.
Mark
On 05/12/2022 11:16, Rainer Jung wrote:
Hi there,
the following tests fail for me when using tcnative 2.0.2
Hi there,
the following tests fail for me when using tcnative 2.0.2 build against
OpenSSL 3.1.0-alpha1:
testHIGH: Expected 127 ciphers but got 137 for the specification 'HIGH'
testMEDIUM: Expected 10 ciphers but got 0 for the specification 'MEDIUM'
testSpecification01: Expected 115 ciphers
FYI: the performance check TestMessageBytes.testConversionPerformance()
seems to fail sometimes for various Linux variants and JVM versions. It
fails in 13 out of 116 combinations of Linux distro, JVM version and
provider and connector.
When failing, it complains, that the non-optimised
Am 20.10.2022 um 11:01 schrieb Rémy Maucherat:
On Fri, Oct 7, 2022 at 11:28 AM Mark Thomas wrote:
Hi all,
I don't think there is a need to make a decision on this quickly, but
based on past experience and the current discussions about Jakarta EE 11
I think this is something we need to start
https://bz.apache.org/bugzilla/show_bug.cgi?id=66281
Thanks,
Rainer
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Am 28.09.2022 um 11:40 schrieb Rainer Jung:
Hi all,
I observe the following behavior:
NIO2 connector with HTTP2 and JSSE.
Client is (recent) curl or recent Firefox or Chrome.
If I call a JSP, that sleep for 8 seconds before responding, then the
client gets after 5 seconds:
curl: (92) HTTP
Hi all,
I observe the following behavior:
NIO2 connector with HTTP2 and JSSE.
Client is (recent) curl or recent Firefox or Chrome.
If I call a JSP, that sleep for 8 seconds before responding, then the
client gets after 5 seconds:
curl: (92) HTTP/2 stream 1 was not closed cleanly before end
Am 20.09.2022 um 20:35 schrieb Mark Thomas:
The proposed Apache Tomcat 10.1.0-M20 release is now available for
voting.
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
Am 22.09.2022 um 11:06 schrieb Mark Thomas:
The proposed Apache Tomcat 10.0.25 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
Am 22.09.2022 um 11:21 schrieb Rémy Maucherat:
The proposed Apache Tomcat 9.0.66 release is now available for voting.
The notable changes compared to 9.0.65 are:
- Add support for authenticating WebSocket clients with an HTTP forward
proxy when establishing a connection to a WebSocket
Am 22.09.2022 um 22:01 schrieb Rainer Jung:
I see a problem and wanted to do a quick heads up before double checking:
When looking at the MBeans via the jmxproxy in the manager webapp,
especially the
Catalina:type=RequestProcessor,worker="http-nio-",name=HttpRequest, version 9.0
I see a problem and wanted to do a quick heads up before double checking:
When looking at the MBeans via the jmxproxy in the manager webapp,
especially the
Catalina:type=RequestProcessor,worker="http-nio-",name=HttpRequest,
version 9.0.66 misses lots of attributes we previously made
Hi Jean-Frederic,
Am 20.07.2022 um 08:47 schrieb jean-frederic clere:
On 20/07/2022 00:16, Rainer Jung wrote:
Roughly the same pattern I saw for TC 10.0 now also seen for TC 10.1.
May be something wrong in apr? Which apr version are you using?
- the same APR library for tcnative 1.2.35
Roughly the same pattern I saw for TC 10.0 now also seen for TC 10.1.
Am 18.07.2022 um 12:09 schrieb Rainer Jung:
Hi there,
this is just an info, at this point probably not a showstopper. The
topic is crashes in tcnative 1.2 and 2.0 for TC 10.0 during shutdown
after TLS unit tests.
Details
Hi there,
this is just an info, at this point probably not a showstopper. The
topic is crashes in tcnative 1.2 and 2.0 for TC 10.0 during shutdown
after TLS unit tests.
Details:
I ran the TC unit tests for latest 9.x, 10.x and 10.1.x with tcnative
1.2.35 OpenSSL 1.1.1q, 1.2.35 OpenSSL
Sorry for being late to the game and the following is not a show stopper:
I finally had the chance of running the unit tests with 2.0.1. I also
used it for TC 9 and 10, although I know the primary target is 10.1. But
the docs for tcnative 2 do not indicate it is only for 10.1.
I got the
Sorry wrong list :(
Am 30.06.2022 um 10:59 schrieb Rainer Jung:
Hi there,
I ran the pytest suite on SLES 12+15 and RHEL 7+8 for 2.4.54 plus
OpenSSL 1.1.1p. Ran it for event, worker and prefork and with OpenSSL
1.1.1 and 3.0 in the client.
I observe sporadic segmentation faults on all
Hi there,
I ran the pytest suite on SLES 12+15 and RHEL 7+8 for 2.4.54 plus
OpenSSL 1.1.1p. Ran it for event, worker and prefork and with OpenSSL
1.1.1 and 3.0 in the client.
I observe sporadic segmentation faults on all of those platforms and for
all MPMs and all OpenSSL versions in the
Hi all,
first a short reminder: I added logging of a request id to the mod_jk
log to ease correlation with other Apache logs, like the access log. It
was motivated by a discussion with Chris, although the end result wasn't
exactly what he liked most.
After thinking more about the feature I
Am 27.05.2022 um 23:11 schrieb Christopher Schultz:
Rainer,
On 5/27/22 4:45 PM, Rainer Jung wrote:
Hi there,
I suspect there is a ponter deref typo in the source code of the ISAPI
redirector. Suggested patch would be:
diff --git a/native/iis/jk_isapi_plugin.c b/native/iis/jk_isapi_plugin.c
The following commit(s) were added to refs/heads/main by this push:
new 29650817a Standardize variable name for jk_ws_service_t args
to "s".
29650817a is described below
commit 29650817a04af7d3ae72f9d561660a5457fc307c
Author: Rainer Jung
AuthorDate: Fri May 27 14:43:47 2022 +0200
S
Hi there,
I suspect there is a ponter deref typo in the source code of the ISAPI
redirector. Suggested patch would be:
diff --git a/native/iis/jk_isapi_plugin.c b/native/iis/jk_isapi_plugin.c
index c0d7a4353..4978a0b85 100644
--- a/native/iis/jk_isapi_plugin.c
+++
Hi all,
I added logging of a request id to mod_jk log to ease correlation with
other Apache logs, like the access log. It was motivated by a discussion
with Chris, although the end result wasn't exactly what he liked most.
Currently there is no useful ID logged for IIS, because I don't know
Am 13.05.2022 um 15:20 schrieb Mark Thomas:
On 13/05/2022 12:16, Mark Thomas wrote:
This looks like a bug to me.
Confirmed. It is this one:
https://bugs.openjdk.java.net/browse/JDK-8245169
This has been fixed in jdk8u-dev as part of this issue:
Am 12.05.2022 um 22:57 schrieb Rémy Maucherat:
On Thu, May 12, 2022 at 9:14 PM Rainer Jung wrote:
... for me with Java 1.8.0 332 (various OpenJDK builds) on TC 9.0.63 and
10.0.21, platform various Linuxes and also Solaris Sparc. It does not
fail for Java 11 and also not for Oracle Java 1.8.0
... for me with Java 1.8.0 332 (various OpenJDK builds) on TC 9.0.63 and
10.0.21, platform various Linuxes and also Solaris Sparc. It does not
fail for Java 11 and also not for Oracle Java 1.8.0 331.
Testsuite: org.apache.tomcat.util.net.jsse.TestPEMFile
Tests run: 5, Failures: 0, Errors: 1,
1 - 100 of 2003 matches
Mail list logo
