Conversation
- Remove McpSseShutdownConfiguration (WebMvcSseServerTransportProvider is @deprecated forRemoval=true in Spring AI 2.0) - Switch integration tests to protocol=STREAMABLE + HttpClientStreamableHttpTransport, and update docs
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Summary
McpSseShutdownConfigurationand its test —WebMvcSseServerTransportProvideris@Deprecated(forRemoval=true)in Spring AI 2.0; the graceful-shutdown workaround it provided becomes a compilation time-bomb on the next Spring AI releaseprotocol=SSE+HttpClientSseClientTransporttoprotocol=STREAMABLE+HttpClientStreamableHttpTransport, aligning tests with the Spring AI 2.0 defaultintegrations/page.adoc: document Streamable HTTP as the default (endpoint/mcp), remove the now-unnecessary mcp proxy workaround, and add a deprecation callout for SSE users explaining the shutdown behaviour and migration pathImpact on SSE clients
SSE transport (
protocol: SSE) continues to work during normal operation. The only regression is on server shutdown: withoutMcpSseShutdownConfiguration, Tomcat waits up to 30 s before force-closing open SSE streams rather than draining them gracefully.This is the pre-workaround behaviour and is documented in the updated reference page. Users still on SSE should migrate to
protocol: STREAMABLE.Closes: #2047