Web session in jdbc store not deleted

[jprio]

Hi,

We're using WF10 and we'd like to use this configuration for our web cache :

<cache-container name="web" default-cache="jdbc" module="org.wildfly.clustering.web.infinispan">
                    <transport lock-timeout="60000"/>
                    <local-cache name="concurrent">
                        <file-store passivation="true" purge="false"/>
                    </local-cache>
                    <invalidation-cache name="jdbc">
                        <transaction mode="BATCH"/>
                        <binary-keyed-jdbc-store data-source="H2DS" fetch-state="false" passivation="false" preload="false" purge="false" shared="true" singleton="false">
                            <property name="databaseType">
                                H2
                            </property>
                            <property name="createTableOnStart">
                                true
                            </property>
                            <binary-keyed-table prefix="SESSIONS">
                                <id-column name="id" type="VARCHAR"/>
                                <data-column name="datum" type="BINARY"/>
                                <timestamp-column name="version" type="BIGINT"/>
                            </binary-keyed-table>
                        </binary-keyed-jdbc-store>
                    </invalidation-cache>
                </cache-container>

We can see our sessions persisted in the store, but they are never deleted from the db when expired. Is there anything wrong in my configuration ?

Regards,

JP

[pferraro]

There is nothing specifically wrong with your configuration, though your id-column really ought to be a numeric type.  Additionally, you can replace your "databaseType" property with the attribute: dialect="H2".

Web sessions are indeed deleted from the database on expiration.  It's a common misconception that the binary-keyed-jdbc-store stores a database record per session.  This is not the case.  This cache store implementation stores a database record for each hash bucket, where the cache entries of a given bucket are stored within the "datum" field.  When a web session expires, this triggers an update of this record, not a deletion.

I strongly encourage you to update to WF11, whose jdbc-store implementation maps each cache entry to a separate database record.  This is far more efficient than the binary-keyed-jdbc-store.

[jprio]

Thank you Paul for the explanation. I just tested with WF11 and it works as you said : one row per session, deleted at expiration.

JP