Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Jersey update from 3.1.8 to 3.1.9 performance regression when using the JVM http.proxyHost mechanism #5814

Closed
ripdajacker opened this issue Dec 3, 2024 · 2 comments
Closed

Jersey update from 3.1.8 to 3.1.9 performance regression when using the JVM http.proxyHost mechanism #5814

ripdajacker opened this issue Dec 3, 2024 · 2 comments

Comments

@ripdajacker
Copy link

This PR introduced the regression: #5749

The referenced fix introduces a map from java.util.URL to a Lock. That has the side effect of calling getInetAddress(url.host), which significantly impacts the performance if you are running the JVM with a proxy with -Dhttp.proxyHost and -Dhttp.proxyPort.

Before the call to hashCode the JVM handled the proxy connection transparently.
@ripdajacker ripdajacker mentioned this issue Dec 3, 2024
Closed
@ripdajacker
Copy link
Author

ripdajacker commented Dec 3, 2024 •
edited
Loading

Fixed in: #5815

@senivam senivam linked a pull request Dec 3, 2024 that will close this issue
Use string as hashcode in lock map in HttpUrlConnectorProvider #5815
Closed
@jansupol
Copy link
Contributor

Fixed by #5794

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use string as hashcode in lock map in HttpUrlConnectorProvider ripdajacker/jersey
2 participants
@ripdajacker @jansupol