-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Async actions do not work with tomcat #47
Comments
I ran into the same issue with Tomcat 7 when trying to use Atmosphere library long pull support. I wasn't able to resolve it but, I think you mentioned that DynamicMapperFilter may be the cause in a another issue. I think that may be the case. I didn't have any luck marking the dispatch servlet and the stripe filter with async support. I would be interested in a fix for this. Although, it not a big issue for me at the moment. |
Problem is that DMF wraps a DispatcherServlet directly and delegates to it, bypassing the servlet's lifecycle management (the dispatcher is not managed by the container). Tomcat somehow detects the servlet anyway, and as it's not declared as async, it throws an exception. |
I'm having the same problem. I'm writing a simple Ginger service that I want to make async. I set async-supported to true in web.xml for both the servlet (GingerServlet) and the filter (RequestContextFilter). My AH post is here: https://answerhub.corp.ebay.com/questions/262377/asynchronous-servlets-in-raptor-255.html I don't see DynamicMapperFilter anywhere in scope so I don't think I'm using that. |
Could you please post the stack trace ? Or even better, provide a SSCCE ? There is a (failing) test for async actions in the build, but it's using DMF. |
I have the same issue - 2018-05-07 07:48:57 SEVERE org.apache.catalina.core.StandardWrapperValve invoke Servlet.service() for servlet [functional] in context with path [] threw exception |
@prai-git Have you tried not using the DynamicMappingFilter? The way it is designed causes other issues also. |
You have to mention async option as true. By default it's not true.
|
Async actions don't work in tomcat because tomcat complains that "a servlet or filter in the chain is not async".
Stack (tomcat 8) :
The text was updated successfully, but these errors were encountered: