[Bug 65757] Async WriteListener#onWritePossible never called

https://bz.apache.org/bugzilla/show_bug.cgi?id=65757 Remy Maucherat changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 65773] WINDOW_UPDATE NOT SENT

https://bz.apache.org/bugzilla/show_bug.cgi?id=65773 Mark Thomas changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REOPENED

[Bug 65179] HTTP2:WINDOW_UPDATE not sent when receiving http2 requests over unknown url

https://bz.apache.org/bugzilla/show_bug.cgi?id=65179 --- Comment #5 from Mark Thomas --- *** Bug 65773 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. -

[Bug 65755] Users sporadically receive responses intended for other user's session

https://bz.apache.org/bugzilla/show_bug.cgi?id=65755 --- Comment #2 from dimitrios.psymar...@atos.net --- Hi, We have already checked if there are any possible "leaked" references to the request/response/session objects outside of their normal scope, but this doesn't seem to be the case. Just to

Re: DataSourceUserDatabase questions

On Sat, Jan 1, 2022 at 10:07 PM Mark Thomas wrote: > > On 01/01/2022 20:05, Rémy Maucherat wrote: > > On Sat, Jan 1, 2022 at 8:20 PM Mark Thomas wrote: > >> > >> Hi all, > >> > >> Probably questions for Rémy but any input welcome. > >> > >> I'm looking at SpotBugs and it has a few warning for thi

Re: DataSourceUserDatabase questions

4 Jan 2022 13:03:57 Rémy Maucherat : Thanks for the sync improvements. As for the problematic scenarios, sequences like create/remove/create seem confusing when reading the code but do work. Agreed. I think I was getting confused by the possible ways to break it with concurrent requests.

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

Thanks for the additional trace. That looks like a different issue. This is next on my TODO list so hopefully I'll have something for you to test later today. Mark On 03/01/2022 19:11, Rainer Jung wrote: Unfortunately I can still reproduce a deadlock on 8.5. I saw the non-8.5 update a few min

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

On 03/01/2022 21:19, Rémy Maucherat wrote: On Mon, Jan 3, 2022 at 12:32 PM Mark Thomas wrote: Sort of related, I am wondering about the build environment. We have seen an issue with downstream building with Java 11 and there are difficulties building 8.5.x particularly with a clean install

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

On Tue, Jan 4, 2022 at 4:09 PM Mark Thomas wrote: > > On 03/01/2022 21:19, Rémy Maucherat wrote: > > On Mon, Jan 3, 2022 at 12:32 PM Mark Thomas wrote: > > > > >> Sort of related, I am wondering about the build environment. We have > >> seen an issue with downstream building with Java 11 and the

[tomcat] branch 8.5.x updated: Fix potential deadlock with concurrent new frames and close for stream

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 1b2d056 Fix potential deadlock with concurrent new

[tomcat] branch 9.0.x updated: Fix potential deadlock with concurrent new frames and close for stream

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 39e4c4e Fix potential deadlock with concurrent new

[tomcat] branch 10.0.x updated: Fix potential deadlock with concurrent new frames and close for stream

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 d77177d Fix potential deadlock with concurrent n

[tomcat] branch main updated: Fix potential deadlock with concurrent new frames and close for stream

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 aa48dd9 Fix potential deadlock with concurrent new f

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

Hi Rainer, I think I have this additional issue fixed. If you could test and let me know how you get on that would be great. Thanks, Mark On 04/01/2022 13:58, Mark Thomas wrote: Thanks for the additional trace. That looks like a different issue. This is next on my TODO list so hopefully I'

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

Hi Mark, Am 04.01.2022 um 16:29 schrieb Mark Thomas: Hi Rainer, I think I have this additional issue fixed. If you could test and let me know how you get on that would be great. Great! LGTM, more than 200 iterations without deadlock. Before it neded about 3-10 iterations. Thanks a bunch,

[GitHub] [tomcat-jakartaee-migration] squarewav opened a new issue #24: Copyright and Derived Works

squarewav opened a new issue #24: URL: https://github.com/apache/tomcat-jakartaee-migration/issues/24 Can you provide a statement in the README.md that describes the changes made by this tool? It is customary for software EULAs to include language like the following: `5. You m

[GitHub] [tomcat-jakartaee-migration] ebourg commented on issue #24: Copyright and Derived Works

ebourg commented on issue #24: URL: https://github.com/apache/tomcat-jakartaee-migration/issues/24#issuecomment-1005121746 > Can it be said that the only changes this tool makes are to package names? Yes > Does it change method signatures, parameter types Yes and yes, i