Skip to content

[Solace] Close the HTTP response content stream in BrokerResponse#39404

Open
PDGGK wants to merge 1 commit into
apache:masterfrom
PDGGK:fix-solace-brokerresponse-leak
Open

[Solace] Close the HTTP response content stream in BrokerResponse#39404
PDGGK wants to merge 1 commit into
apache:masterfrom
PDGGK:fix-solace-brokerresponse-leak

Conversation

@PDGGK

@PDGGK PDGGK commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Fixes #39403

BrokerResponse read the SEMP HTTP response body through a BufferedReader but never closed the underlying InputStream. Since BrokerResponse.fromHttpResponse is fed HttpResponse#getContent() and SempBasicAuthClientExecutor (getQueueResponse / createQueueResponse / createSubscriptionResponse) never disconnects the response or closes the stream elsewhere, every SEMP call leaked the HTTP response content stream.

This wraps the reader in a try-with-resources so the stream is always closed once the body has been read. Stream#lines() already surfaces read errors as UncheckedIOException, so the constructor keeps the same unchecked failure contract; a close failure is wrapped the same way.

Added BrokerResponseTest verifying that the content is still parsed correctly and that the input stream is closed after construction.

BrokerResponse read the SEMP HTTP response body via a BufferedReader but
never closed the underlying InputStream, so every SEMP call leaked the
HTTP response content stream (the HttpResponse is never disconnected
elsewhere either). Wrap the reader in try-with-resources so the stream
is always closed once the body has been read, and add a regression
test.
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a resource leak in the BrokerResponse class where the HTTP response input stream was not being closed after being read. By wrapping the stream processing in a try-with-resources block, the fix ensures that connections are released properly, improving the stability and resource efficiency of SEMP calls.

Highlights

  • Resource Management: Implemented a try-with-resources block in BrokerResponse to ensure the HTTP response content stream is properly closed after reading, preventing resource leaks.
  • Testing: Added a new test class, BrokerResponseTest, which verifies that the content is parsed correctly and that the input stream is closed upon construction.
New Features

🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@PDGGK

PDGGK commented Jul 21, 2026

Copy link
Copy Markdown
Contributor Author

assign set of reviewers

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates BrokerResponse to use a try-with-resources block when reading the response content, ensuring that the underlying InputStream is closed and preventing potential HTTP connection leaks. It also introduces a new test class BrokerResponseTest to verify that the stream is properly closed and that null content is handled correctly. There are no review comments to address, and I have no further feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

@github-actions

Copy link
Copy Markdown
Contributor

Assigning reviewers:

R: @Abacn for label java.

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

  • stop reviewer notifications - opt out of the automated review tooling
  • remind me after tests pass - tag the comment author after tests pass
  • waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Solace BrokerResponse leaks the SEMP HTTP response content stream

1 participant