<div dir="ltr">I&#39;ve continued digging into my issue and noticed that the default DistributableSessionManager uses the org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager, which I guess comes from the module parameter in the cache-container definition.<div><br></div><div>Part of my problem is that I am trying to invalidate() the session returned by the SessionManager, but when I do a SessionManager.getSession(sessionId), it returns an DistributableImmutableSession whose invalidate() method intentionally does nothing.</div><div><br>So how can I invalidate a session?  Is there no way to invalidate a session by sessionId with the DistributableSessionManager?  If so, how?  If not, how do I define a SessionManager that would give me access that?  </div><div><br></div><div>Thanks,</div><div><br>Eric</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 19, 2017 at 11:38 AM, Eric B <span dir="ltr">&lt;<a href="mailto:ebenzacar@gmail.com" target="_blank">ebenzacar@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Further to a previous post for session problems in my application, I believe some of my issues relate to the DistributableSessions that are being used by Wildfly.  However, in my configuration file, I have my web cache defined as a local cache:<div><br></div><div><br><div><br></div><div><div>        &lt;subsystem xmlns=&quot;urn:jboss:domain:<wbr>infinispan:4.0&quot;&gt;</div><div>            &lt;cache-container name=&quot;server&quot; aliases=&quot;singleton cluster&quot; default-cache=&quot;default&quot; module=&quot;org.wildfly.<wbr>clustering.server&quot;&gt;</div><div>                &lt;transport lock-timeout=&quot;60000&quot;/&gt;</div><div>                &lt;replicated-cache name=&quot;default&quot; mode=&quot;SYNC&quot;&gt;</div><div>                    &lt;transaction mode=&quot;BATCH&quot;/&gt;</div><div>                &lt;/replicated-cache&gt;</div><div>            &lt;/cache-container&gt;</div><div>            &lt;cache-container name=&quot;web&quot; default-cache=&quot;passivation&quot; module=&quot;org.wildfly.<wbr>clustering.web.infinispan&quot;&gt;</div><div>                &lt;local-cache name=&quot;passivation&quot;&gt;</div><div>                    &lt;locking isolation=&quot;REPEATABLE_READ&quot;/&gt;</div><div>                    &lt;transaction mode=&quot;BATCH&quot;/&gt;</div><div>                    &lt;file-store passivation=&quot;true&quot; purge=&quot;false&quot;/&gt;</div><div>                &lt;/local-cache&gt;</div><div>                &lt;local-cache name=&quot;persistent&quot;&gt;</div><div>                    &lt;locking isolation=&quot;REPEATABLE_READ&quot;/&gt;</div><div>                    &lt;transaction mode=&quot;BATCH&quot;/&gt;</div><div>                    &lt;file-store passivation=&quot;false&quot; purge=&quot;false&quot;/&gt;</div><div>                &lt;/local-cache&gt;</div><div>            &lt;/cache-container&gt;</div></div></div><div>...</div><div>...</div><div><br></div><br>I see that undertow comes with an InMemorySessionManager, but not entirely sure how to enable it.  Do I have to go through the effort of creating my own ServletExtension and configuring it in the META-INF/services/io.undertow.<wbr>servlet.ServletExtension or is there an out-of-the-box way of enable functionality that already exists via the config file?<br><br>Thanks,<br><br>Eric</div>
</blockquote></div><br></div>