[Bug 63022] Nio2Endpoint(SocketProcessorBase) for async request doesn't decrement LimitLatch while handling socket that is already closed

https://bz.apache.org/bugzilla/show_bug.cgi?id=63022 --- Comment #11 from Remy Maucherat --- Ok, so this explains what I saw. The statement was way too convoluted for me, so I indeed misunderstood it a bit. -- You are receiving this mail because: You are the assignee for the bug. --

[Bug 63022] Nio2Endpoint(SocketProcessorBase) for async request doesn't decrement LimitLatch while handling socket that is already closed

https://bz.apache.org/bugzilla/show_bug.cgi?id=63022 --- Comment #10 from Pankaj --- I think you misunderstood my last comment. The test case was updated just to make it more relevant to our use case however patch provided earlier does FIX this issue. -- You are receiving this mail because: You

[Bug 63022] Nio2Endpoint(SocketProcessorBase) for async request doesn't decrement LimitLatch while handling socket that is already closed

https://bz.apache.org/bugzilla/show_bug.cgi?id=63022 Remy Maucherat changed: What|Removed |Added Resolution|--- |FIXED Status|NEEDINFO

[Bug 63022] Nio2Endpoint(SocketProcessorBase) for async request doesn't decrement LimitLatch while handling socket that is already closed

https://bz.apache.org/bugzilla/show_bug.cgi?id=63022 --- Comment #7 from Pankaj --- Created attachment 36343 --> https://bz.apache.org/bugzilla/attachment.cgi?id=36343&action=edit Web application(SimpleWebApp) to recreate bug -- You are receiving this mail because: You are the assignee for th

[Bug 63022] Nio2Endpoint(SocketProcessorBase) for async request doesn't decrement LimitLatch while handling socket that is already closed

https://bz.apache.org/bugzilla/show_bug.cgi?id=63022 Pankaj changed: What|Removed |Added Attachment #36338|0 |1 is obsolete|

[Bug 63022] Nio2Endpoint(SocketProcessorBase) for async request doesn't decrement LimitLatch while handling socket that is already closed

https://bz.apache.org/bugzilla/show_bug.cgi?id=63022 --- Comment #6 from Pankaj --- Attached is an updated test case (AsyncConnectionCount.zip) where async request first writes xml data to stream before closing the socket. Connection count is still not getting decremented. We are actually hitti

[Bug 63022] Nio2Endpoint(SocketProcessorBase) for async request doesn't decrement LimitLatch while handling socket that is already closed

https://bz.apache.org/bugzilla/show_bug.cgi?id=63022 Remy Maucherat changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #5 from Remy Mau

[Bug 63022] Nio2Endpoint(SocketProcessorBase) for async request doesn't decrement LimitLatch while handling socket that is already closed

https://bz.apache.org/bugzilla/show_bug.cgi?id=63022 Pankaj changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #4 from Pankaj --- Thanks fo

[Bug 63022] Nio2Endpoint(SocketProcessorBase) for async request doesn't decrement LimitLatch while handling socket that is already closed

https://bz.apache.org/bugzilla/show_bug.cgi?id=63022 --- Comment #3 from Remy Maucherat --- Created attachment 36340 --> https://bz.apache.org/bugzilla/attachment.cgi?id=36340&action=edit NIO2 close patch Simplify the socket close for NIO2, which would probably fix bad side effects like seen h

[Bug 63022] Nio2Endpoint(SocketProcessorBase) for async request doesn't decrement LimitLatch while handling socket that is already closed

https://bz.apache.org/bugzilla/show_bug.cgi?id=63022 Remy Maucherat changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #2 from Remy Mau

[Bug 63022] Nio2Endpoint(SocketProcessorBase) for async request doesn't decrement LimitLatch while handling socket that is already closed

https://bz.apache.org/bugzilla/show_bug.cgi?id=63022 --- Comment #1 from Pankaj --- Created attachment 36338 --> https://bz.apache.org/bugzilla/attachment.cgi?id=36338&action=edit Web application(SimpleWebApp) to recreate bug -- You are receiving this mail because: You are the assignee for th