The issue is about replicated-cache in fail-over tests.
WildFly is started in clustered mode using a replicated cache for replicating HTTP session data across cluster nodes; all 4 nodes in the cluster are initialized with the following cli script:

embed-server --server-config=standalone-ha.xml
/subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp)
/subsystem=infinispan/cache-container=web/replicated-cache=testRepl:add()
/subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ)
/subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=transaction:write-attribute(name=mode, value=BATCH)
/subsystem=infinispan/cache-container=web/replicated-cache=testRepl/store=file:add()
/subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=testRepl)

The test is run with wildfly-18.​0.0.Final.zip;
The same tests run with version wildfly-17.​0.1.Final.zip do not have any problem;
hence this looks like a regression;

As usual, we test that the serial value stored in the replicated cache is incremented at every call: when this is not true, we say we have a sampling error;

Here are the runs that exhibit this issue:

• **22.82% Fail Rate with WildFly-18 ** eap-7.x-clustering-http-session-shutdown-repl#23
• **0% Fail Rate with WildFly-17 ** eap-7.x-clustering-http-session-shutdown-repl#24

We also repeated the tests to make sure it can be reproduced:

• **22.75% Fail rate with WildFly-18 ** eap-7.x-clustering-http-session-shutdown-repl#26
• **0% Fail Rate with WildFly-17 ** eap-7.x-clustering-http-session-shutdown-repl#25