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
FutureUtil should wait until timeout ends instead of throwing first timeout exception. ExceptionHandler should decide to throw exception or not. Caller should decide to cancel other futures or not.
client request and split brain test for countdownLatch
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
osgi: removed com.eclipsesource.json from Import-Packages

com.eclipsesource.json should not appear in the list of
imported packages since it is relocated by the maven
shade plugin as com.hazelcast.com.eclipsesource.json
when committing collection transactions add collection item to the collection container instead of transactional item, this was causing serialization problems while migration. fixes #3603
Update MapContainer.nearCacheEnabled when the MapConfig is set
Session ID must use cryptographically strong random number generator
fixes #3776
#3767 Unnecessary object instantiation removed.
Thanks to @cmuramoto for pointing this out!
Transactional collections error messages are enhanced
enhancement for issue #3659 by using "ConcurrentSkipListMap" instead of using "SortedSet" for keys and "ConcurrentMap" for values on SortedIndexStore
checkstyle fix for issue #3659
merged with latest master
Pulled out HazelcastClientInstance

Fixes #3781

Also improved documentation and minor cleanups