This failure happens when send/receive multiple messages via wss connection with a simple echo server. I'm not sure if it is the "significant issue" mentioned in temporary fix for JDK-8157045.

If send with ws connection, there is a different problem. See the comments.

OnError will be triggered as following stacktrace when several messages has been sent. The limit number (now 42001) changes with the total length of messages sent.
Note that:
This happened if total size > 40000 with multiple messages.
There is no such issue if only send 1 big message > 40000)

java.lang.IllegalArgumentException: limit: 42001
at java.net.http.WSShared.checkRegion(java.httpclient@9-ea/WSShared.java:134)
at java.net.http.WSSharedPool$Pooled.share(java.httpclient@9-ea/WSSharedPool.java:99)
at java.net.http.WSSharedPool$Pooled.share(java.httpclient@9-ea/WSSharedPool.java:79)
at java.net.http.WSReceiver.getData(java.httpclient@9-ea/WSReceiver.java:124)
at java.net.http.WSReceiver.react(java.httpclient@9-ea/WSReceiver.java:82)
at java.net.http.WSSignalHandler.lambda$new$1(java.httpclient@9-ea/WSSignalHandler.java:80)
at java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@9-ea/ThreadPoolExecutor.java:1158)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@9-ea/ThreadPoolExecutor.java:632)
at java.lang.Thread.run(java.base@9-ea/Thread.java:843)