We have a client app that is fetching a new session in one request. After seeing the response line providing the JSESSIONID cookie, the app forms and sends a second request with that JSESSIONID. But sometimes that JSESSIONID is not available or found by the second request. It seems there is some timing issue at play here if the second request occurs too quickly. We have batch mode enabled on our cache config:
<cache-container name="web" default-cache="passivation" module="org.wildfly.clustering.web.infinispan"> <local-cache name="passivation"> <transaction mode="BATCH"/> <file-store passivation="true" purge="false"/> </local-cache> ...
- JBoss Enterprise Application Platform (EAP) 7.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.