Skip to content

bmcweb: Fix LTPC connection handling#71

Open
anshaw9 wants to merge 1 commit into
integ_sp8from
fix-bmcweb-ltpc-max-connection
Open

bmcweb: Fix LTPC connection handling#71
anshaw9 wants to merge 1 commit into
integ_sp8from
fix-bmcweb-ltpc-max-connection

Conversation

@anshaw9

@anshaw9 anshaw9 commented Jul 2, 2026

Copy link
Copy Markdown
Collaborator

Summary:

  • Fix an off-by-one error in the HTTPS connection limit check.
  • Allow exactly 200 active HTTPS connections before rejecting new requests.
  • Close connections on write failures to release connection slots promptly.

Problem:

During LTPC stress testing, WebUI and Redfish became unresponsive while SSH remained accessible because bmcweb rejected new HTTPS connections after reaching its internal connection limit.

Root Cause:

  • connectionCount is incremented before the limit check, causing the 200th connection to be rejected due to an off-by-one condition.
  • Write failures could delay connection cleanup, causing connection slots to remain occupied longer than necessary.

Validation:

  • Built successfully.
  • Verified the connection limit check allows exactly 200 active HTTPS connections.
  • Verified connections are closed on write failures.

Allow exactly 200 active HTTPS connections by fixing
an off-by-one error in the connection limit check.

Also close connections on write failures to ensure
connection slots are released promptly and prevent
WebUI and Redfish from becoming unresponsive after
LTPC stress testing.

Signed-off-by: Anand Kumar Shaw <anshaw@amd.com>
@anshaw9

anshaw9 commented Jul 2, 2026

Copy link
Copy Markdown
Collaborator Author

@ashok
@ashray
@mo
Please review.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants