Fix XEP-0124 BOSH compliance: overactivity exception, ack handling, sentElements cleanup

[Copilot]

Openfire's BOSH implementation had several deviations from XEP-0124 around request acknowledgements, overactivity enforcement, and retransmission buffer management.

Changes

Overactivity check allows pause/terminate exception (§11)

Per spec, clients MAY send one additional simultaneous request if it is a pause or terminate. Previously the check fired at pendingConnections >= maxRequests unconditionally, rejecting valid pause/terminate requests from clients already at the limit.

// Before
if (pendingConnections >= maxRequests) { overactivity = TOO_MANY_SIM_REQS; }

// After — pause/terminate gets +1 headroom
final boolean isPauseOrTerminate = connection.isTerminate() || connection.getPause() != null;
final int maxSimultaneousRequests = isPauseOrTerminate ? maxRequests + 1 : maxRequests;
if (pendingConnections >= maxSimultaneousRequests) { overactivity = TOO_MANY_SIM_REQS; }

Parse client ack attribute from request bodies (§9.2)

Added HttpBindBody.getAck() to expose the client's acknowledged RID. When present, acknowledged entries are now pruned from the sentElements retransmission buffer rather than relying solely on a size cap of maxRequests.

Omit redundant ack in responses (§9.1)

"the connection manager SHOULD NOT include an 'ack' attribute in any response if the value would be the 'rid' of the request being responded to"

asBodyText() and createEmptyBody() now accept the responding-to RID and suppress the ack attribute when it would be identical—the common steady-state case.

Tests

Added HttpBindBodyTest covering getAck() (present/absent/invalid/initial-value), getRid(), and isPoll() variants.

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

[guusdk]

@copilot I have raised these new JIRA tickets for the fixes that you created:

• https://igniterealtime.atlassian.net/browse/OF-3219
• https://igniterealtime.atlassian.net/browse/OF-3220
• https://igniterealtime.atlassian.net/browse/OF-3221

Evaluate them to see if they correctly describe the issues that you fixed.

To replace this PR, create three new PRs, each addressing a single JIRA issue. Use the issue number in the title of each commit. Also include a reference to the corresponding JIRA issue (using a javadoc @see tag) to the new, individual unit tests where applicable.

[Copilot]

@guusdk I've opened a new pull request, #3224, to work on those changes. Once the pull request is ready, I'll request review from you.

[guusdk]

@copilot that is not what I wanted. Lets try something else. Create a new PR that only holds three commits, which includes each of the changes discussed here.

[Copilot]

@guusdk I've opened a new pull request, #3228, to work on those changes. Once the pull request is ready, I'll request review from you.

[guusdk]

Copilot didn't exactly do what I wanted. I've manually created the desired PR in #3229 - that PR replaces this PR.