The current configuration for the infinispan cache for web session replication is waiting on the initial state transfer. If this goes wrong for some reason, i.e. an existing session which can not serialized, the complete start will fail.
This can affect all applications which are correctly working.
As this can be a configuration issue, like the timeout for the initial-state-transfer, or a bug in the application code because the session must be serializable, it should be possible to start the server even if threre are some sessions failing.
With the current configuration options there is no way to configure the cache in a way that the cache is not waiting for the ST or to have the ST asynchronous that the server starts and 'only' the session replication will not be fully loaded.
As an enhancement such configuration should be possible.