Why can't the Wildfly server handle concurrent REST requests after programmatic login

[mark.brooks.180]

I previously asked why after establishing a httpSession that REST requests no longer ran concurrently. Paul referred me to the section “Session Concurrency” in the document

https://github.com/wildfly/wildfly/blob/master/docs/src/main/asciidoc/_high-availability/subsystem-support/Distributable_Web_Applications.adoc#session-concurrency

By relaxing transaction isolation from REPEATABLE_READ to READ_COMMITTED on the associated cache configuration fixed my problem and REST requests began operating in a concurrent fashion.  The related question is why after performing a programmatic login using the HttpServletRequest’s login function does the same problem arise.  The call to login(“username”, “password”) establishes a session after which REST requests no longer run concurrently. 

Here are the fundamentals of my environment:

Wildfly Server Info: Wildfly-17.0.0.Final running on Windows 10 using standalone, high availability configuration specified in standalone-ha.xml

[rhusar]

Can you reproduce the behavior with WildFly 18 or 19 as well? Downloads · WildFly

[mark.brooks.180]

I haven't tried to reproduce the problem under Wildfly 18, or 19 yet.  I'll give it a shot when I get a chance and report the findings.

[mark.brooks.180]

I ran the same test using Wildfly-19.0.0.Beta1  The problem does not appear in this version.  The multi-threaded test ran in a concurrent fashion as expected.  I'll test under Wildfly 18 first thing Monday morning.

[mark.brooks.180]

I ran the test using Wildfly-18.0.1.Final.  It works.  The multi-threaded test ran in a concurrent fashion as expected.  It looks like I'll be changing versions.

[rhusar]

Perfect.