2.6.2 SNAPSHOT
There was a bug in the client where the config of the map was retrieved on the full name including prefix.
And therefor the map config is not found and therefor the nearache was not found. So the fix makes sure that
the original map name is used to lookup the mapconfig from the config.
Merge pull request #623 from pveentjer/fix/2.x/near-cache-in-client-incorrect

There was a bug in the client where the config of the map was retrieved ...
fixes #644
Merge remote-tracking branch 'origin/master'
fixes #644
fixed map.putAll eviction (#670)
added test for issue #670
fixed spring hazelcast cache set after changing behaviour of set with
zero ttl
changes set behaviour to old one (before changing logic of zero ttl)
Test cleanup.
Updated readme
fixed and optimized reconnect call handling

if we push a block of calls the reconnection calls are check for a
response but the never were written to cluster. also on single write the
reconnection calls is checked twice with the same call. this will check
all reconnection calls for a response (also not submitted one).

if their are more reconnection calls pending the duplicates check after
every write causes that it takes too long to complete: 100ms *
NumberOfReconnectionCalls * NumberOfReconnectionCalls
on reconnection we also have to reorder the blocked calls queue
Merge pull request #676 from notz/fix-client-reconnect

2.x Client reconnection fix
Initial support for queue monitoring
Adds the socketaddress to the SocketException message for improved logging
Made the cluster monitor startup configurable
Removed the processableQueue overload protection
Changed logging level to Info for the queue monitor