@Async is defaulting to RequestHandlerMapping

[orubel]

Am running spirngboot 3.2.5 with JDK 21 and when I add a Completeablefuture and @async to an endpoint mapped with SimpleUrlHandlerMapping, the DispatcherServlet is trying to use RequestHandlerMapping.

Now I know that this is supposed to work with webflux and see nothing that says 'async' requires RequestHandlerMapping. This seems to be a 'bug' (but I have been wrong before)

12:50:17.346 [http-nio-127.0.0.1-auto-1-exec-4] DEBUG o.s.security.web.FilterChainProxy - Secured GET /v1.0/user/show
12:50:17.347 [http-nio-127.0.0.1-auto-1-exec-4] DEBUG o.s.web.servlet.DispatcherServlet - GET "/v1.0/user/show", parameters={}
12:50:17.347 [http-nio-127.0.0.1-auto-1-exec-4] WARN  o.s.web.servlet.PageNotFound - No mapping for GET /v1.0/user/show
12:50:17.347 [http-nio-127.0.0.1-auto-1-exec-4] DEBUG o.s.web.servlet.DispatcherServlet - Completed 404 NOT_FOUND
12:50:17.350 [http-nio-127.0.0.1-auto-1-exec-4] DEBUG o.s.security.web.FilterChainProxy - Securing GET /error
12:50:17.351 [http-nio-127.0.0.1-auto-1-exec-4] DEBUG o.s.w.s.m.m.a.RequestMappingHandlerMapping - Mapped to io.beapi.api.controller.BeapiErrorController#error(HttpServletRequest, HttpServletResponse)
12:50:17.351 [http-nio-127.0.0.1-auto-1-exec-4] DEBUG o.s.w.s.m.m.a.RequestMappingHandlerMapping - Mapped to io.beapi.api.controller.BeapiErrorController#error(HttpServletRequest, HttpServletResponse)
12:50:17.352 [http-nio-127.0.0.1-auto-1-exec-4] DEBUG o.s.w.s.m.m.a.RequestMappingHandlerMapping - Mapped to io.beapi.api.controller.BeapiErrorController#error(HttpServletRequest, HttpServletResponse)
12:50:17.352 [http-nio-127.0.0.1-auto-1-exec-4] DEBUG o.s.security.web.FilterChainProxy - Secured GET /error
12:50:17.352 [http-nio-127.0.0.1-auto-1-exec-4] DEBUG o.s.web.servlet.DispatcherServlet - "ERROR" dispatch for GET "/error", parameters={}
12:50:17.352 [http-nio-127.0.0.1-auto-1-exec-4] DEBUG o.s.w.s.m.m.a.RequestMappingHandlerMapping - Mapped to io.beapi.api.controller.BeapiErrorController#error(HttpServletRequest, HttpServletResponse)

This DOESN"T affect the other endpoints that are also mapped with SimpleUrlHandlerMapping; only the one I added 'async' to.

It is also making it past initial filters (JwtRequestFilter, RequestInitializationFilter) and are not throwing an error BUT is not making it to the interceptor.

Thus I can assume that something in the securityfilterchain is causing this issue. Should I move this bug to spring-security????

[mhalbritter]

Spring Boot 3.2.5 is out of open source support. Please upgrade to a OSS supported Spring Boot version and see if the problem persists. If it does, please create a minimal reproducer so that we can take a look. Also see this wiki page. Thanks!

[orubel]

Spring Boot 3.2.5 is out of open source support. Please upgrade

Thanks. I upgraded to 3.3.10 and still same issue. I will try to work on a min viable project to demonstrate. Will require me to build out the requestHandler for simpleurlHandlerMapping so it may not be as 'minimal' as you want but it will demonstrate the issue.

[orubel]

@mhalbritter min viable project can be found here : https://github.com/orubel/min-viable-demo

can test via the following curl call:
curl -v -b ./cookies.txt --request GET "http://localhost:8080/test/show"

So the 'min viable' does work... BUT does not use the security filterchain and thats where I suspect the problem occurs as both of my other filters were called fine but something in the security filter chain doesn't route: the RequestHandler is never called (doesn't even make it to the prehandle method in the interceptor)

Should I resubmit with security installed??? Would be easier to just show the whole project at that point as am not sure which filter is causing issue

Is there an easy way to get an error from security filter? Maybe even to know which filter is throwing issue.

[orubel]

You know NVM. Increased my logging and problem may exist in existing filter I maintain.

closing

[orubel]

As a followup, turns out I forgot to add a check for parsing CompletableFuture in my RequestHandler. Fixed the other errors and is running great :)