Refine Throwable handling in spring-websocket

[maczikasz]

spring-framework/spring-websocket/src/main/java/org/springframework/web/socket/handler/ExceptionWebSocketHandlerDecorator.java

Line 97 in 3a0f309

// ignore

ExceptionWebSocketHandlerDecorator swallows all exceptions including OOM, I had a problem where all my apps went into zombie mode, because they did not crash with OOM as expected, because they were swallowed

[rstoyanchev]

The handling (and swallowing) of exceptions and closing the session is what the decorator was designed to do. We can however allow different treatment for OutOfMemoryError and allow that to propagate.

[maczikasz]

That would be awesome, my biggest problem is that spring automatically applies the decorator on every websocket connection in : org.springframework.web.socket.server.support.WebSocketHttpRequestHandler

and I did not see any elegant solution to disable this, without performing open hearth surgery using reflection

[rstoyanchev]

I've lowered Throwable handling to Exception in a number of places in spring-websocket including the decorator. I've also added a protected method to WebSocketHttpRequestHandler to allow overriding the decorators added.

[maczikasz]

Thank, you, will keep an eye out for the release