Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Allow HTTP Connection Pool to be Configurable

Description

The HTTP connection pool in mod-circulation is hardcoded to 100. This value is too low for heavy environments that have to make high number of HTTP requests to mod-circulation-storage and mod-inventory-storage. This can cause a major performance bottleneck for a single instance of mod-circulation.

Expose an environment variable that will set the maximum connection pool size upon startup. Variable name can be HTTP_MAXPOOLSIZE.

Hint for dev:

Environment

None

Potential Workaround

None

Attachments

3

Checklist

hide

Activity

Show:

Olamide Kolawole April 2, 2025 at 5:51 PM

Yes, this can be closed!

Tetiana Gusar April 1, 2025 at 10:18 AM

Hi this has been fixed now, can we close this ticket?

Roman Barannyk March 24, 2025 at 10:34 AM

tested on snapshot, the connection pool size has been successfully configured:

Roman Barannyk March 19, 2025 at 3:35 PM
Edited

Prepared a PR and tested on the dev Rancher environment. The connection pool size was successfully overridden using the HTTP_MAXPOOLSIZE variable:

and with invalid value:

Khalilah Gambrell March 18, 2025 at 1:04 PM

Hey , please see 's comments. Please contact him with additional questions.

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Vega

Fix versions

Release

Ramsons (R2 2024) Service Patch #1

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created March 6, 2025 at 11:07 PM
Updated April 2, 2025 at 5:51 PM
Resolved March 24, 2025 at 10:56 AM
TestRail: Cases
TestRail: Runs