[Bug 61886] 7.0.83 Calling [asyncComplete()] is not valid for a request with Async state [MUST_COMPLETE]

https://bz.apache.org/bugzilla/show_bug.cgi?id=61886 --- Comment #11 from Mark Thomas --- NPE on Tomcat (actually just webapp) stop should be fixed now too. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 61886] 7.0.83 Calling [asyncComplete()] is not valid for a request with Async state [MUST_COMPLETE]

https://bz.apache.org/bugzilla/show_bug.cgi?id=61886 --- Comment #10 from Mark Thomas --- I believe I've fixed the ConcurrentModificationException. Still investigating the NPE. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 61886] 7.0.83 Calling [asyncComplete()] is not valid for a request with Async state [MUST_COMPLETE]

https://bz.apache.org/bugzilla/show_bug.cgi?id=61886 --- Comment #9 from Konstantin Kolinko --- (In reply to Konstantin Kolinko from comment #8) > Testing current Tomcat 8.5-dev @r1820546 That ConcurrentModificationException was when running with Java 7u80. With Java

[Bug 61886] 7.0.83 Calling [asyncComplete()] is not valid for a request with Async state [MUST_COMPLETE]

https://bz.apache.org/bugzilla/show_bug.cgi?id=61886 --- Comment #8 from Konstantin Kolinko --- Testing current Tomcat 8.5-dev @r1820546 A ConcurrentModificationException is printed on the console, but not in the logs. Nothing interesting in the logs. Not attaching them

[Bug 61886] 7.0.83 Calling [asyncComplete()] is not valid for a request with Async state [MUST_COMPLETE]

https://bz.apache.org/bugzilla/show_bug.cgi?id=61886 --- Comment #7 from Konstantin Kolinko --- Created attachment 35659 --> https://bz.apache.org/bugzilla/attachment.cgi?id=35659=edit catalina.2018-01-08.log.txt Testing current Tomcat 9.0-dev @r1820558. Generally -

[Bug 61886] 7.0.83 Calling [asyncComplete()] is not valid for a request with Async state [MUST_COMPLETE]

https://bz.apache.org/bugzilla/show_bug.cgi?id=61886 Mark Thomas changed: What|Removed |Added Resolution|--- |FIXED

[Bug 61886] 7.0.83 Calling [asyncComplete()] is not valid for a request with Async state [MUST_COMPLETE]

https://bz.apache.org/bugzilla/show_bug.cgi?id=61886 --- Comment #5 from Konstantin Kolinko --- (In reply to Konstantin Kolinko from comment #4) > > Fixing that appears to have fixed this bug too. > > Confirmed. I cannot reproduce the WARNING message now. Good. I added

[Bug 61886] 7.0.83 Calling [asyncComplete()] is not valid for a request with Async state [MUST_COMPLETE]

https://bz.apache.org/bugzilla/show_bug.cgi?id=61886 Konstantin Kolinko changed: What|Removed |Added Status|RESOLVED|REOPENED

[Bug 61886] 7.0.83 Calling [asyncComplete()] is not valid for a request with Async state [MUST_COMPLETE]

https://bz.apache.org/bugzilla/show_bug.cgi?id=61886 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 61886] 7.0.83 Calling [asyncComplete()] is not valid for a request with Async state [MUST_COMPLETE]

https://bz.apache.org/bugzilla/show_bug.cgi?id=61886 --- Comment #2 from Mark Thomas --- I can repeat this. I'm looking into why it happens. The spec is clear about when it is legal to call this method, but unclear as to what to do if it is called illegally. Generally that

[Bug 61886] 7.0.83 Calling [asyncComplete()] is not valid for a request with Async state [MUST_COMPLETE]

https://bz.apache.org/bugzilla/show_bug.cgi?id=61886 Konstantin Kolinko changed: What|Removed |Added OS||All ---