Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support configuring WebSocket message buffer size [SPR-11575] #16199

Closed
spring-projects-issues opened this issue Mar 18, 2014 · 1 comment
Closed
Assignees
Labels
in: web type: enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Mar 18, 2014

Rossen Stoyanchev opened SPR-11575 and commented

As explained in #16152, stomp.js and the Dart STOMP client split messages larger than 16K. #16152 will ensure support for re-assembling such messages on the server side with a configurable buffer size.

However, Tomcat's default WebSocket message buffer size is 8K (Jetty is 64K), which means the support for large messages still won't work unless Tomcat is configured for 16K. Therefore when using the Spring Framework STOMP over WebSocket support, 16K would be a better default to be auto-configured in the Java config and XML namespace.


Affects: 4.0.2

Issue Links:

  • #16152 Support receiving fragmented STOMP frames
@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Mar 24, 2014

Rossen Stoyanchev commented

For the concrete purpose of this ticket it was sufficient to add support for configuring the size of text and binary messages through the WebSocket session.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web type: enhancement
Projects
None yet
Development

No branches or pull requests

2 participants