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.

Sign up for GitHub

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

Jump to bottom

Improve the internal Jersey Client to use a Connection Pool #22003

Closed
1 of 2 tasks
poorbarcode opened this issue Jan 31, 2024 · 2 comments
Closed
1 of 2 tasks

Improve the internal Jersey Client to use a Connection Pool #22003

poorbarcode opened this issue Jan 31, 2024 · 2 comments

Comments

@poorbarcode
Copy link
Contributor

poorbarcode commented Jan 31, 2024 •
edited

Search before asking

  • I searched in the issues and found nothing similar.

Motivation

As many connections as there are requests are used by the internal Jersey Client.

Solution

No response

Alternatives

No response

Anything else?

No response

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@lhotari
Copy link
Member

lhotari commented Feb 9, 2024

pulsar-client-admin uses AsyncHttpClient , I created #22041 for addressing that.

Jetty client is used in the Pulsar Proxy for proxying /admin endpoint.

Where do we have a Jersey client?

@lhotari
Copy link
Member

lhotari commented Feb 9, 2024

This issue seems to be a duplicate of #22041. The AsyncHttpClient is used as a Jersey client connector in pulsar-client-admin. I'll close this ticket since #22041 contains a better issue description.

@lhotari lhotari closed this as completed Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lhotari @poorbarcode