Hi i wonder why @controllerAdvice can not catch exception thrown in websocket-stomp

[horanga]

I'm developing a chat service using Spring WebSocket/STOMP, and I have a question about the exception handling design.

Current Understanding

• I understand that WebSocket uses a different protocol from HTTP
• Spring's @ControllerAdvice works well with HTTP-based controllers for global exception handling
• WebSocket/STOMP exceptions are not caught by @ControllerAdvice

Technical Question

I'd like to understand the architectural decisions behind this design:

1. Why can't @ControllerAdvice intercept WebSocket/STOMP exceptions?
2. Is this due to different execution contexts between HTTP and WebSocket?

This is not a bug report but rather a question to understand the framework's design decisions better.

[bclozel]

Hi @horanga

WebSocket/STOMP exceptions should be processed by @ControllerAdvice classes with @MessageExceptionHandler, see reference doc. If this is not the case, please share a minimal sample application that reproduces the problem, as a GitHub repository or a zip file attached to this issue.

Thanks!

[rstoyanchev]

Closing for now, as @ControllerAdvice is supported.