Duplicate of https://github.com/spring-projects/spring-framework/issues/29375 But old issue is not resolved, although it being closed.
Hey, we are still experiencing this issue with Spring Boot 3.0.6, which uses spring-messaging and spring-websocket with version 6.0.8. Here is an excerpt from our logs:
023-05-11T14:50:29.682Z INFO 1 --- [MessageBroker-4] o.s.w.s.c.WebSocketMessageBrokerStats : WebSocketSession[928 current WS(2983)-HttpStream(3)-HttpPoll(6), 125916 total, 483 closed abnormally (483 connect failure, 0 send limit, 56579 transport error)], stompSubProtocol[processed CONNECT(120381)-CONNECTED(118726)-DISCONNECT(2413)], stompBrokerRelay[null], inboundChannel[pool size = 8, active threads = 0, queued tasks = 0, completed tasks = 1089279], outboundChannel[pool size = 8, active threads = 0, queued tasks = 0, completed tasks = 1467036], sockJsScheduler[pool size = 4, active threads = 1, queued tasks = 907, completed tasks = 3746831]
Originally posted by @daniel-naegele in https://github.com/spring-projects/spring-framework/issues/29375#issuecomment-1544171608
Comment From: daniel-naegele
Another hint for solving this bug: I think this issue arises, when a client sends the next connect before the last connection was established and somewhere a counter decrease is missing (or one counter increment is too much)
Comment From: snicoll
As we've hint previously, we need a sample that lets us reproduce the problem you've described.
You can share it with us by attaching a zip to this issue or pushing the code to a GitHub repository.
Comment From: spring-projects-issues
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.
Comment From: spring-projects-issues
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.