Created attachment 36351 [details] the test case according to jsr 340 P57, the following filter config will make this filter call order: AsyncCompleteFilter_2 -> AsyncCompleteFilter_3 -> AsyncCompleteFilter -> AsyncCompleteFilter_2 -> AsyncCompleteFilter_3 however, only AsyncCompleteFilter_2 -> AsyncCompleteFilter_3 -> AsyncCompleteFilter are called ```xml <servlet> <servlet-name>AsyncComplete</servlet-name> <servlet-class>servlet1.Asyn1</servlet-class> <async-supported>true</async-supported> </servlet> <servlet-mapping> <servlet-name>AsyncComplete</servlet-name> <url-pattern>/AsyncComplete</url-pattern> </servlet-mapping> <filter> <filter-name>AsyncCompleteFilter</filter-name> <filter-class>servlet1.Filter1</filter-class> <async-supported>true</async-supported> </filter> <filter-mapping> <filter-name>AsyncCompleteFilter</filter-name> <servlet-name>AsyncComplete</servlet-name> </filter-mapping> <filter> <filter-name>AsyncCompleteFilter_2</filter-name> <filter-class>servlet1.Filter2</filter-class> <async-supported>true</async-supported> </filter> <filter-mapping> <filter-name>AsyncCompleteFilter_2</filter-name> <servlet-name>AsyncComplete</servlet-name> <url-pattern>/*</url-pattern> </filter-mapping> <filter> <filter-name>AsyncCompleteFilter_3</filter-name> <filter-class>servlet1.Filter3</filter-class> <async-supported>true</async-supported> </filter> <filter-mapping> <filter-name>AsyncCompleteFilter_3</filter-name> <servlet-name>AsyncComplete</servlet-name> <url-pattern>/*</url-pattern> </filter-mapping> ```
The expected behaviour is awaiting clarification from the Servlet EG. *** This bug has been marked as a duplicate of bug 49922 ***