Repository navigation
CXF-8272: Don't fail a one-way invocation if the response stream can'… - #3586
Merged
Merged
Conversation
reta
approved these changes
Oct 15, 2026
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
2 participants
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.
…t be drained
After a one-way SOAP call, CXF reads and throws away any leftover response bytes. This is only so the HTTP connection can be reused for the next request. In some environments the JDK had already closed that response stream, so this tidy-up step threw “stream is closed”. That made the whole call fail, even though the request had been delivered and accepted.
The fix makes the tidy-up step best-effort. If draining fails, CXF logs it at FINE level, still closes the stream, and lets the call succeed. HTTP error responses are still reported as before. The patch also adds a test that recreates the “stream already closed” case.