During initialization the NearCacheService will set the bloomFilterBits it will use. This is invoked during resolution of the storage media.

Unfortunately, InvalidatedNearRemoteCache asks for the bloomFilterBits when it is created, which is before this step, so it always thinks the bits are empty. This causes it not to track updates properly.

This was not noticed because the updateBloomFilter method ALWAYS sends an empty byte[] for its bits, no matter what. This would cause an extra remote call every time as well as clearing out the server's bloom filter so it would miss updates.

We need to prevent it from always sending the bloom filter update and also set the bits properly in the constructor instead of at the resolution of storage media.