The bug is caused by a race condition in tomcat and is a tomcat bug which is fixed and released in tomcat version 10.1.39 according to the tomcat changelog:

https://tomcat.apache.org/tomcat-10.1-doc/changelog.html

Please refer to coyote fixes in 10.1.37:
Fix: Fix a race condition in the handling of HTTP/2 stream reset that could cause unexpected 500 responses. (markt)

https://github.com/apache/tomcat/commit/63187839521a26c1b7d0a1c076ce6a331cf8b035#diff-3b95b31753cf4d298203bdda2637bfa4c044f34d11ad99eb037c5e581a2a829f

The latest JWS version we have is JWS 6.1(Tomcatv10.1.36). Is this bug going to be backported to this version, or will there be a new version?