[Bug 64082] Nio2Endpoint for async request doesn't clear OutputBuffer when socket has already been closed (response mixup)

2020-02-12 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64082 Mark Thomas changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|---

[Bug 64082] Nio2Endpoint for async request doesn't clear OutputBuffer when socket has already been closed (response mixup)

2020-02-12 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64082 --- Comment #12 from william.crow...@roguewave.com --- Please close this issue. We cannot provide a valid test case. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 64082] Nio2Endpoint for async request doesn't clear OutputBuffer when socket has already been closed (response mixup)

2020-01-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64082 --- Comment #11 from william.crow...@roguewave.com --- Bear with us for a moment as we are trying to get a viable test case together. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 64082] Nio2Endpoint for async request doesn't clear OutputBuffer when socket has already been closed (response mixup)

2020-01-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64082 --- Comment #10 from william.crow...@roguewave.com --- Thanks for your reply. I will post an update to this issue tomorrow. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 64082] Nio2Endpoint for async request doesn't clear OutputBuffer when socket has already been closed (response mixup)

2020-01-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64082 --- Comment #9 from Christopher Schultz --- (In reply to william.crowell from comment #8) > > Are you also able to reliably reproduce the error without RECYCLE_FACADES > > enabled? > > Yes, it happens on each test run. Great. > > Tomcat

[Bug 64082] Nio2Endpoint for async request doesn't clear OutputBuffer when socket has already been closed (response mixup)

2020-01-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64082 --- Comment #8 from william.crow...@roguewave.com --- > Are you also able to reliably reproduce the error without RECYCLE_FACADES > enabled? Yes, it happens on each test run. > Tomcat (usually) properly protects these objects from

[Bug 64082] Nio2Endpoint for async request doesn't clear OutputBuffer when socket has already been closed (response mixup)

2020-01-24 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64082 --- Comment #7 from Christopher Schultz --- (In reply to william.crowell from comment #4) > Setting org.apache.catalina.connector.RECYCLE_FACADES to true did work. Excellent. Since it "works", are you also able to reliably reproduce the error

[Bug 64082] Nio2Endpoint for async request doesn't clear OutputBuffer when socket has already been closed (response mixup)

2020-01-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64082 --- Comment #6 from william.crow...@roguewave.com --- For a simple test case are you looking for application code? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 64082] Nio2Endpoint for async request doesn't clear OutputBuffer when socket has already been closed (response mixup)

2020-01-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64082 --- Comment #5 from Remy Maucherat --- I described the scenario in my comment, the application code is most likely not aware that the async is done. To know where the problem comes from a simple test case would be useful. -- You are

[Bug 64082] Nio2Endpoint for async request doesn't clear OutputBuffer when socket has already been closed (response mixup)

2020-01-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64082 --- Comment #4 from william.crow...@roguewave.com --- Setting org.apache.catalina.connector.RECYCLE_FACADES to true did work. Do you know why that fixed the issue? I am also concerned about the performance impact of setting that flag to true.

[Bug 64082] Nio2Endpoint for async request doesn't clear OutputBuffer when socket has already been closed (response mixup)

2020-01-21 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64082 Remy Maucherat changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #3 from Remy

[Bug 64082] Nio2Endpoint for async request doesn't clear OutputBuffer when socket has already been closed (response mixup)

2020-01-17 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64082 --- Comment #2 from Remy Maucherat --- You are presenting what could be an issue in a complex and confusing IMO. So let's start over. The changes to isClosed is likely not relevant and this will not be changed. They ensure that the socket

[Bug 64082] Nio2Endpoint for async request doesn't clear OutputBuffer when socket has already been closed (response mixup)

2020-01-17 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64082 --- Comment #1 from william.crow...@roguewave.com --- For reference: Tomcat 8.5.3 - 8.5.31 and 9.0.0 - 9.0.8: ... @Override public boolean isClosed() { return !getSocket().isOpen(); } ... Tomcat 8.5.32 - 8.5.37 and 9.0.9 - 9.0.14 ...