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

Issue #6470 - remove ByteBufferPool usage from MessageInputStream #6485

Closed

Conversation

lachlan-roberts
Copy link
Contributor

@lachlan-roberts lachlan-roberts commented Jun 30, 2021

#6470
Signed-off-by: Lachlan Roberts lachlan@webtide.com

Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
@gregw
Copy link
Contributor

gregw commented Jun 30, 2021

Is this a fix or just and avoidance of the problem? ie are there buffers that can be pooled?

@gregw gregw linked an issue Jun 30, 2021 that may be closed by this pull request
@gregw gregw added this to In progress in Jetty 9.4.43 FROZEN via automation Jun 30, 2021
Copy link
Contributor

@gregw gregw left a comment

Choose a reason for hiding this comment

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

yeah - not convinced we should take out the whole buffer pooling to fix this.
Please prepare another PR that just fixes the adding EOF to the pool and we can compare.

Jetty 9.4.43 FROZEN automation moved this from In progress to Review in progress Jun 30, 2021
@gregw
Copy link
Contributor

gregw commented Jun 30, 2021

I think we should close in favour of #6486

Jetty 9.4.43 FROZEN automation moved this from Review in progress to Done Jun 30, 2021
@joakime joakime deleted the jetty-9.4.x-6470-MessageInputStream branch July 12, 2021 12:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

java.nio.ReadOnlyBufferException
2 participants