In https://issues.redhat.com/browse/UNDERTOW-2401 an attempt has been made to apply an upstream fix from Jasper. Contents of that change reside in a single commit:

• https://github.com/undertow-io/jastow/commit/b05f7446e65664edc96b73945ba17fa7db67027e (Jun 13, 2024)
• https://github.com/apache/tomcat/commit/e7a1d655ed9f7d186f58dab655d0e120495db03e (Jul 26, 2016)

However if we follow the commit log for the affected class we can see that Jasper reverted the commit that was applied to Jastow in the next commit of the file's commit history (Dec 22, 2016):

• https://github.com/apache/tomcat/commit/18b53513d76def3e49a2c11200eb17acda8a0c5f

Eventually a new solutions to the issue seems to be created in (Jan 27, 2017):

• https://github.com/apache/tomcat/commit/487ade279cc3e460bab10606782ce7ac719fc5ff

We are experiencing an issue with an old JSF application that is now returning an errorMessage: "java.lang.IllegalStateException: FacesContext already released". We have drilled it down to this specific change in Jastow that is related to the commits above.

• https://github.com/undertow-io/jastow/pull/105

This commit seems to be the only change to Jastow between the versions 2.0.14 and 2.0.15 (where 2.0.15 is the current version of Jastow at the moment of writing).

Suggested solution:

It seems like the wrong commit has been picked in order to fix the solution. Follow the upstream commit log an apply the "final/improved" solution/fix.