https://bz.apache.org/bugzilla/show_bug.cgi?id=61768
--- Comment #2 from Herbert Wespi <herbert.we...@swisscom.com> --- I do have a different point of view here. I also thought in the beginning, that it is the fault of the Jersey Framework, because if I would implement an asynchronous request myself, it would be easy to get it work for tomcat. However, if I read corretly the chapter 5.6 of the Servlet 3.0 Specification, then it looks like that the application/Framework is allowed to use the response object as long as complete on AsyncContext is not called. 5.6 Lifetime of the Response Object Each response object is valid only within the scope of a servlet’s service method, or within the scope of a filter’s doFilter method, unless the associated request object has asynchronous processing enabled for the component. If asynchronous processing on the associated request is started, then the request object remains valid until complete method on AsyncContext is called. Containers commonly recycle response objects in order to avoid the performance overhead of response object creation. The developer must be aware that maintaining references to response objects for which startAsync on the corresponding request has not been called, outside the scope described above may lead to non-deterministic behavior. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
