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
SseEmitter: connection closed after first event #25987
Comments
5.2.10.RELEASE
The regression is due to optimizations in Jackson codecs and converters, issue #25910. |
Thanks a lot for quick update, @rstoyanchev |
It's look that there is the same regression with controller producing multipart. The server response is truncated after any jackson part body (the boundary after this part is missing, all remaining parts are ignored). |
Yes this will impact all cases in Spring MVC where Jackson is used to write but the response needs to remain open. |
This should be fixed now for 5.2.11 and 5.3.1. In the mean time as a workaround you could disable the @Bean
public Jackson2ObjectMapperBuilderCustomizer om() {
return builder -> builder.featuresToDisable(JsonGenerator.Feature.AUTO_CLOSE_TARGET);
} |
It seems like there is a regression introduced into
SseEmitter
in latest5.2.10.RELEASE
(apparently #25442), it now returns to the client only first SSE event.How to reproduce
2.3.4.RELEASE
and Spring Framework5.2.9.RELEASE
2.3.4.RELEASE
and Spring Framework5.2.10.RELEASE
(overriding with<spring-framework.version>5.2.10.RELEASE</spring-framework.version>
)Reproducible all the time. Please advice if this is a regression or
SseEmitter
semantics has changed (would appreciate documentation pointers) or more details are needed, thank you.The text was updated successfully, but these errors were encountered: