You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Anees Shaikh <an...@loginextsolutions.com> on 2018/05/05 11:50:06 UTC

[Tomcat 8.5] : Calling [asyncError()] is not valid for a request with Async state [COMPLETING]

Hi,

I am using using *tomcat-embed-core-8.5.11*, with JDK 8, OS : Linux

I am getting following error very frequently. Please can you help.

ERROR [http-nio-auto-1-exec-6] o.a.c.c.CoyoteAdapter:181 : Exception while
processing an asynchronous request java.lang.IllegalStateException: Calling
[asyncError()] is not valid for a request with Async state [COMPLETING] at
org.apache.coyote.AsyncStateMachine.asyncError(AsyncStateMachine.java:397)
at org.apache.coyote.AbstractProcessor.action(AbstractProcessor.java:389)
at org.apache.coyote.Request.action(Request.java:391) at
org.apache.catalina.core.AsyncContextImpl.setErrorState(AsyncContextImpl.java:380)
at org.apache.catalina.connector.CoyoteAdapter.asyncDispatch(CoyoteAdapter.java:180)
at org.apache.coyote.AbstractProcessor.dispatch(AbstractProcessor.java:221)
at org.apache.coyote.AbstractProcessorLight.process(
AbstractProcessorLight.java:53) at org.apache.coyote.AbstractProtocol$
ConnectionHandler.process(AbstractProtocol.java:798) at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1434)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
As per your documentation.



As per tomcat documentation for 8.0.25 is the above issue fixed ?
Tomcat 8.0.25 (markt)

   - [image: Fix:] 58192
   <http://bz.apache.org/bugzilla/show_bug.cgi?id=58192>: Correct a
   regression in the previous fix for 58023
   <http://bz.apache.org/bugzilla/show_bug.cgi?id=58023>. Ensure that
   classes are associated with their manifest even if the class file is first
   read (and cached) without the manifest. (markt)
   - [image: Fix:] *Fix thread safety issue in
   the AsyncContext implementation that meant a sequence
   of start();dispatch(); calls using non-container threads could result in a
   previous dispatch interfering with a subsequent start. (markt)*


Thanks and regards,
Anees Shaikh
Technical Lead - Loginext Solutions Pvt. Ltd
+91 7875043336

-- 
This message (including any attachments) contains confidential information 
intended for a specific individual and purpose, and is protected by law and 
is the property of LogiNext. If you are not the intended recipient, you 
should delete this message. Any disclosure, copying, or distribution of 
this message, or the taking of any action based on it, is strictly 
prohibited.