On 03/01/2022 14:20, Rainer Jung wrote:
Unfortunately it seems the deadlock has just moved:
Thanks for the quick turn-around.
I'll continue looking for a fix for this.
Mark
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.ap
Am 03.01.2022 um 15:00 schrieb Mark Thomas:
On 03/01/2022 13:05, Rainer Jung wrote:
Am 03.01.2022 um 12:33 schrieb Mark Thomas:
On 03/01/2022 11:17, Rainer Jung wrote:
Thanks Marc.
In the meantime, I can also say, that it happens for TC 8.5 using
JSSE or OpenSSL and NIO or NIO2. I did not t
On 03/01/2022 13:05, Rainer Jung wrote:
Am 03.01.2022 um 12:33 schrieb Mark Thomas:
On 03/01/2022 11:17, Rainer Jung wrote:
Thanks Marc.
In the meantime, I can also say, that it happens for TC 8.5 using
JSSE or OpenSSL and NIO or NIO2. I did not try APR.
Unfortunately I can still reproduce
Am 03.01.2022 um 12:33 schrieb Mark Thomas:
On 03/01/2022 11:17, Rainer Jung wrote:
Thanks Marc.
In the meantime, I can also say, that it happens for TC 8.5 using JSSE
or OpenSSL and NIO or NIO2. I did not try APR.
Unfortunately I can still reproduce on TC 8.5 even without the sync
patch
On 03/01/2022 11:17, Rainer Jung wrote:
Thanks Marc.
In the meantime, I can also say, that it happens for TC 8.5 using JSSE
or OpenSSL and NIO or NIO2. I did not try APR.
Unfortunately I can still reproduce on TC 8.5 even without the sync
patch you mentioned below.
Drat. Can you post the s
Thanks Marc.
In the meantime, I can also say, that it happens for TC 8.5 using JSSE
or OpenSSL and NIO or NIO2. I did not try APR.
Unfortunately I can still reproduce on TC 8.5 even without the sync
patch you mentioned below. The code curretly under test has:
diff --git a/java/org/apache/co
On 03/01/2022 09:45, Mark Thomas wrote:
Hi Rainer,
Thanks for finding this. It isn't something I have seen in my testing. I
think this is something that needs to be fixed before the January set of
releases.
From the stack trace, it looks like the root cause is locks being
obtained in an in
Hi Rainer,
Thanks for finding this. It isn't something I have seen in my testing. I
think this is something that needs to be fixed before the January set of
releases.
From the stack trace, it looks like the root cause is locks being
obtained in an inconsistent order - a classic deadlock.
I
I can reproduce with 8.5.x head and the following JVMs:
Zulu 1.8.0_312-b07:
OpenJDK Runtime Environment (Zulu 8.58.0.13-CA-solaris) (build
1.8.0_312-b07)
OpenJDK 64-Bit Server VM (Zulu 8.58.0.13-CA-solaris) (build 25.312-b07,
mixed mode)
Adopt: 1.8.0_282-b08
openjdk version "1.8.0_282"
OpenJD
