5 Replies Latest reply on Feb 13, 2020 8:30 AM by Radoslav Husar

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

    Mark Brooks Newbie

      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