Re: [tomcat] branch 10.0.x updated: Update Eclipse JDT from 4.20 to 4.22

2022-01-03 Thread Michael Osipov
Am 2022-01-03 um 12:20 schrieb Rémy Maucherat: On Mon, Jan 3, 2022 at 11:53 AM Rainer Jung wrote: For reference: this is probably the ticket about moving JDT (and ECJ) to Java 11: https://bugs.eclipse.org/bugs/show_bug.cgi?id=572389 And this is the parallel mail discussion:

[Bug 65773] WINDOW_UPDATE NOT SENT

2022-01-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65773 Arshiya changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE

Re: [tomcat] branch 10.0.x updated: Update Eclipse JDT from 4.20 to 4.22

2022-01-03 Thread Rémy Maucherat
On Mon, Jan 3, 2022 at 12:32 PM Mark Thomas wrote: > > On 03/01/2022 11:20, Rémy Maucherat wrote: > > On Mon, Jan 3, 2022 at 11:53 AM Rainer Jung wrote: > >> > >> For reference: this is probably the ticket about moving JDT (and ECJ) to > >> Java 11: > >> > >>

Re: [tomcat] branch 8.5.x updated: Improve fix to avoid deadlock reported on some systems

2022-01-03 Thread Rainer Jung
Unfortunately I can still reproduce a deadlock on 8.5. I saw the non-8.5 update a few minutes ago, so maybe more changes are coming. Just wanted to let you know. jstack output attached. Reproduction based on 6285e750e2b640fa9c59c11c09a753a36a5396b8. Am 03.01.2022 um 18:25 schrieb

[tomcat] branch 9.0.x updated: Fix build. Use new sendResetLock in async handler

2022-01-03 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 16847e1 Fix build. Use new sendResetLock in async

[tomcat] branch main updated: Fix build. Use new sendResetLock in async handler

2022-01-03 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 bd0657c Fix build. Use new sendResetLock in async

[tomcat] branch 10.0.x updated: Fix build. Use new sendResetLock in async handler

2022-01-03 Thread markt
This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch 10.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/10.0.x by this push: new 4957254 Fix build. Use new sendResetLock in

[tomcat] branch main updated: Improve fix to avoid deadlock reported on some systems

2022-01-03 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 ca4f298 Improve fix to avoid deadlock reported on

[tomcat] branch 10.0.x updated: Improve fix to avoid deadlock reported on some systems

2022-01-03 Thread markt
This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch 10.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/10.0.x by this push: new 8ba16e0 Improve fix to avoid deadlock reported

[tomcat] branch 9.0.x updated: Improve fix to avoid deadlock reported on some systems

2022-01-03 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 6fa3fd2 Improve fix to avoid deadlock reported on

[tomcat] branch 8.5.x updated: Improve fix to avoid deadlock reported on some systems

2022-01-03 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 6285e75 Improve fix to avoid deadlock reported on

[Bug 65780] CoyoteOutputStream should never throw NullPointerException after AsyncContext.complete() is called

2022-01-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65780 Dapeng Zhang changed: What|Removed |Added Status|NEEDINFO|NEW -- You are receiving this mail

[Bug 65770] Make keys reload automatically

2022-01-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65770 --- Comment #6 from Anders Rundgren --- > The OP recommends using a package that is limited (APR only), fragile > (custom non-daemon watcher thread, suspicious call behavior, and (IMHO) > unnecessary. I'm merely proposing adding this kind of

[tomcat] branch 8.5.x updated: BZ65757: Fix forgotten test case

2022-01-03 Thread remm
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 2bfbbef BZ65757: Fix forgotten test case 2bfbbef

[Bug 65780] CoyoteOutputStream should never throw NullPointerException after AsyncContext.complete() is called

2022-01-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65780 --- Comment #2 from Dapeng Zhang --- A stacktrace is the following: SEVERE: Exception while executing runnable io.grpc.internal.ServerImpl$JumpToApplicationThreadServerStreamListener$1HalfClosed@77087c61 java.lang.NullPointerException

[tomcat] branch 9.0.x updated: BZ65757: Fix forgotten test case

2022-01-03 Thread remm
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 915c2d9 BZ65757: Fix forgotten test case 915c2d9

[tomcat] branch 10.0.x updated: Changelog for 65757

2022-01-03 Thread remm
This is an automated email from the ASF dual-hosted git repository. remm pushed a commit to branch 10.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/10.0.x by this push: new bbd7ebf Changelog for 65757 bbd7ebf is described

[tomcat] branch 10.0.x updated: BZ65757: Fix forgotten test case

2022-01-03 Thread remm
This is an automated email from the ASF dual-hosted git repository. remm pushed a commit to branch 10.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/10.0.x by this push: new 2269c82 BZ65757: Fix forgotten test case 2269c82

[Bug 65770] Make keys reload automatically

2022-01-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65770 --- Comment #5 from Christopher Schultz --- (In reply to Michael Osipov from comment #4) > Why is it not possible to use the background process to > detect mtime change of cert/private key and initiate a connector reload? It is possible. It's

[tomcat] branch main updated: Changelog for 65757

2022-01-03 Thread remm
This is an automated email from the ASF dual-hosted git repository. remm 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 d34f930 Changelog for 65757 d34f930 is described

[tomcat] branch main updated: BZ65757: Fix forgotten test case

2022-01-03 Thread remm
This is an automated email from the ASF dual-hosted git repository. remm 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 e2c2d39 BZ65757: Fix forgotten test case e2c2d39 is

Re: Deadlock in unit tests for TC 8.5.73 on Solaris using zulu 1.8.0_312-b07

2022-01-03 Thread Mark Thomas
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:

Re: Deadlock in unit tests for TC 8.5.73 on Solaris using zulu 1.8.0_312-b07

2022-01-03 Thread Rainer Jung
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

Re: Deadlock in unit tests for TC 8.5.73 on Solaris using zulu 1.8.0_312-b07

2022-01-03 Thread 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 try APR. Unfortunately I can still

Re: Deadlock in unit tests for TC 8.5.73 on Solaris using zulu 1.8.0_312-b07

2022-01-03 Thread Rainer Jung
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

Re: Deadlock in unit tests for TC 8.5.73 on Solaris using zulu 1.8.0_312-b07

2022-01-03 Thread 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 you mentioned below. Drat. Can you post the

Re: [tomcat] branch 10.0.x updated: Update Eclipse JDT from 4.20 to 4.22

2022-01-03 Thread Mark Thomas
On 03/01/2022 11:20, Rémy Maucherat wrote: On Mon, Jan 3, 2022 at 11:53 AM Rainer Jung wrote: For reference: this is probably the ticket about moving JDT (and ECJ) to Java 11: https://bugs.eclipse.org/bugs/show_bug.cgi?id=572389 And this is the parallel mail discussion:

[tomcat] 01/02: Revert ECJ update as 4.22 requires Java 11.

2022-01-03 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 commit 0017e3331636773418083a98767a7259e22394a0 Author: Mark Thomas AuthorDate: Mon Jan 3 11:20:52 2022 + Revert ECJ

[tomcat] 02/02: Fix Java 17 compilation after revert of ECJ update

2022-01-03 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 commit ea57ae94edfd12319a4bf8f88d38bb0f469a7d07 Author: Mark Thomas AuthorDate: Mon Jan 3 11:23:34 2022 + Fix Java 17

[tomcat] branch 9.0.x updated (4da1ceb -> ea57ae9)

2022-01-03 Thread markt
This is an automated email from the ASF dual-hosted git repository. markt pushed a change to branch 9.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git. from 4da1ceb Version updates new 0017e33 Revert ECJ update as 4.22 requires Java 11. new ea57ae9 Fix Java 17

Re: [tomcat] branch 10.0.x updated: Update Eclipse JDT from 4.20 to 4.22

2022-01-03 Thread Rémy Maucherat
On Mon, Jan 3, 2022 at 11:53 AM Rainer Jung wrote: > > For reference: this is probably the ticket about moving JDT (and ECJ) to > Java 11: > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=572389 > > And this is the parallel mail discussion: > >

[tomcat] 01/02: Revert ECJ update as 4.22 requires Java 11.

2022-01-03 Thread markt
This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch 10.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git commit 37cc27f1e8ceaeb298f07cc20722a99f5dd58a81 Author: Mark Thomas AuthorDate: Mon Jan 3 11:11:53 2022 + Revert ECJ

[tomcat] 02/02: Fix Java 17 compilation after revert of ECJ update

2022-01-03 Thread markt
This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch 10.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git commit 9e3fc447ab73303c1b65dfc7f11e8e2f76956441 Author: Mark Thomas AuthorDate: Mon Jan 3 11:18:47 2022 + Fix Java 17

[tomcat] branch 10.0.x updated (d039b4c -> 9e3fc44)

2022-01-03 Thread markt
This is an automated email from the ASF dual-hosted git repository. markt pushed a change to branch 10.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git. from d039b4c Version updates new 37cc27f Revert ECJ update as 4.22 requires Java 11. new 9e3fc44 Fix Java 17

Re: Deadlock in unit tests for TC 8.5.73 on Solaris using zulu 1.8.0_312-b07

2022-01-03 Thread Rainer Jung
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

Re: Deadlock in unit tests for TC 8.5.73 on Solaris using zulu 1.8.0_312-b07

2022-01-03 Thread Mark Thomas
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

Re: [tomcat] branch 10.0.x updated: Update Eclipse JDT from 4.20 to 4.22

2022-01-03 Thread Rainer Jung
For reference: this is probably the ticket about moving JDT (and ECJ) to Java 11: https://bugs.eclipse.org/bugs/show_bug.cgi?id=572389 And this is the parallel mail discussion: https://www.eclipse.org/lists/eclipse-dev/msg11703.html If we roll back the change for TC 10.0 and 9, there is also

Re: [tomcat] branch 10.0.x updated: Update Eclipse JDT from 4.20 to 4.22

2022-01-03 Thread Rainer Jung
It seems JDT 4.22 contains Java 11 compiled classes: compile: ... [javac] /shared/build/dev/tomcat/git/10.0.x/java/org/apache/jasper/compiler/JDTCompiler.java:40: error: cannot access IProblem [javac] import org.eclipse.jdt.core.compiler.IProblem; [javac]

Re: Deadlock in unit tests for TC 8.5.73 on Solaris using zulu 1.8.0_312-b07

2022-01-03 Thread Mark Thomas
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.

[Bug 65780] CoyoteOutputStream should never throw NullPointerException after AsyncContext.complete() is called

2022-01-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65780 Remy Maucherat changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #1 from Remy