Bug Report: Payara 7.2026.10 — include upstream Grizzly fix for StackOverflowError during WebSocket shutdown #8559

Brief Summary

Payara Embedded 7.2026.10 uses Grizzly 5.0.3, which contains a regression that can cause StackOverflowError during Tyrus WebSocket shutdown.

The fix is already merged upstream:

• Fix: Grizzly PR #2394 — Reject write readiness on closing connections, merged November 5, 2026.
• Commit: 79b6a4212c483deb70ad6cb8a40f55948d08ec1a.
• Original report: Grizzly issue #2392.

Please incorporate this fix into Payara through a Grizzly dependency update when a fixed release becomes available, or an appropriate backport. At the time of writing, the fix has not yet been included in a published Grizzly release.

Expected Outcome

WebSocket shutdown should complete or report an I/O error without unbounded synchronous callbacks.

Current Outcome

During connection termination, Grizzly 5.0.3 can return false from canWrite() while synchronously invoking onWritePossible() through notifyCanWrite(). Tyrus can repeatedly retry this contradictory readiness result until StackOverflowError.

The upstream fix makes write-readiness registration report an error for a closing connection rather than reporting write availability, and includes regression coverage.

Payara adopted Grizzly 5.0.3 in Payara PR #8478; Payara’s current pom.xml still references that version.