fix for issue #3659 by using read and write lock on index store
refactor for issue #3659 by reordering methods have similar logic as closer to themselves
checkstyle fix for issue #3659
second fix attempt for issue #3659
refactor of second fix attempt for issue #3659
3th fix attempt for issue #3659 by using "java.util.concurrent.locks.ReentrantReadWriteLock"
refactor for issue #3659 by reordering methods have similar logic as closer to themselves
enhancement for issue #3659 by using "ConcurrentSkipListMap" instead of using "SortedSet" for keys and "ConcurrentMap" for values on SortedIndexStore
checkstyle fix for issue #3659
fix for issue #3659 by ignoring null values at comparable searches on UnsortedIndexStore
unit test for issue #3659 about ignoring null values at comparable searches on SortedIndexStore and UnsortedIndexStore
MaxSizePolicy based on how much free memory there is available
Removed System.out
callable's should get serialized before creating the operation because operation can execute locally and change callable state.
fixes #3812
some tests fixed, since they are relying on not serialized runnable
added a serialization exception check, in order to return the exception to the caller
Merge branch 'master' of https://github.com/hazelcast/hazelcast
Merge branch 'master' of https://github.com/hazelcast/hazelcast
Merge branch 'master' of https://github.com/hazelcast/hazelcast
Merge branch 'master' of https://github.com/hazelcast/hazelcast
Not loading more keys than specified in map's PER_NODE max size policy.