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