Waiting for safe state after shutting down one node, fix #4224
if a callable is sent on a random target, subsequent cancel operation on it should use previously known target
use TargetCallable for refreshable requests
add volatile to response
get refreshed target for cancellation also
Enhanced logging of testMapDestroyIssue764().
Merge pull request #4225 from ajermakovics/mast/entry-proc-test

EntryProcessorTest. Waiting for safe state after shutting down one node
Merge pull request #4231 from ahmetmircik/fix/3.4/futureCancelOnRandomTarget

Fixes cancel operations target address after sending a callable on a random target
JCache Eviction reviewed.
Minor re-phrasing.
Enhancements section re-authored
Heading renamed to resolve cross-reference co....

nflicts…
Extracted assertion logic to private method to cleanup test.
Merge pull request #4284 from Donnerbart/fixIssue4237inMaster

Enhance logging of test to see if issue #4237 is still occuring.
wait safe state for specific node only
Merge branch 'master' of https://github.com/hazelcast/hazelcast