After switching from WF 31 to 35 huge growth of data in infinispan/web/fs.war/data is discovering
Viktoriia Teliuk
Hi all,
After switching to WF 35.0.1.Final and including this fix, we are discovering data growth in
opt/jboss/wildfly/standalone/data/infinispan/web/fs.war/data/ (it increases till the next deploy)
Is it possible that returning an empty result in getExpirationTime for Sessions with a nullable lastAccessTime causes the appearance of never-expiring Sessions?
What could be a reason?
Thank you
Here is our configuration
<subsystem xmlns="urn:jboss:domain:distributable-web:4.0" default-session-management="default" default-single-sign-on-management="default">
<infinispan-session-management name="default" cache-container="web" granularity="SESSION">
<primary-owner-affinity/>
</infinispan-session-management>
<infinispan-single-sign-on-management name="default" cache-container="web" cache="sso"/>
<infinispan-routing cache-container="web" cache="routing"/>
</subsystem>
<cache-container name="web" default-cache="dist" statistics-enabled="true" marshaller="PROTOSTREAM" modules="org.wildfly.clustering.web.infinispan">
<transport lock-timeout="180000"/>
<local-cache name="passivation" statistics-enabled="true">
<file-store passivation="true" purge="false"/>
</local-cache>
<local-cache name="persistent" statistics-enabled="true">
<file-store passivation="false" purge="false"/>
</local-cache>
<local-cache name="concurrent" statistics-enabled="true">
<file-store passivation="true" purge="false"/>
</local-cache>
<replicated-cache name="sso" statistics-enabled="true">
<state-transfer timeout="180000"/>
<expiration interval="0"/>
</replicated-cache>
<distributed-cache name="routing" statistics-enabled="true">
<state-transfer timeout="180000"/>
<expiration interval="0"/>
</distributed-cache>
<distributed-cache name="dist" statistics-enabled="true">
<state-transfer timeout="180000"/>
<expiration interval="0"/>
<file-store/>
</distributed-cache>
</cache-container>