Browse Source
Prior to this commit, Spring Framework would use `Schedulers.elastic()` in places where we needed to process blocking tasks in a reactive environment. With reactor/reactor-core#1804, a new `Schedulers.boundedElastic()` scheduler is available and achieves the same goal with added security; it guarantees that resources are bounded. This commit uses that new scheduler in the standard websocket client, since the underlying API is blocking for the connection phase and we need to schedule that off a web server thread. Closes gh-23661 See gh-23665pull/23772/head
2 changed files with 3 additions and 2 deletions
Loading…
Reference in new issue