Configuring on a AdvancedCacheLoader preload=true and asyn=true cause it to load each entry in the store in a loop, each entry being loaded through a store read. This is caused by the way loadAll is implemented in the AsynLoader: in order to enforce consistency with whatever is in memory it does some special handling. However, this advanced async loader logic is not required during the initial preload, as the async cache loader is empty. </para> <para> The current implemented fix is only an enhancement and not the final resolution. It is still possible that the client try to re-establish the connection if there is a multi-threaded access to the connection from the client. The resolution needs to change the API, which is not possible within a patch or minor release.