[ https://issues.jboss.org/browse/ISPN-7889?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-7889: ------------------------------------ You're right, {{beforeGet}} is not thread-safe, and neither is its {{thenApply()}} callback. I wonder if we need a method {{InvocationStage.afterBothAccept(InvocationStage, InvocationContext, VisitableCommand, InvocationSuccessAction)}} to emulate {{CompletableFuture.allOf}}, something like this: {code} InvocationStage remoteGet(..., InvocationStage previousRemoteGet) { ... return makeStage(asyncValue(rpcManager.invokeRemotely(...)).afterBothAccept(previousRemoteGet, ctx, command, this::storeRemoteValueInContext)); } {code} OTOH this is exactly the kind of thing I had in mind in ISPN-6971 when I made the calls to {{ResponseCollector}} methods protected by a lock, so if possible I'd use something like {{Transport.invokeCommands()}} (the corresponding {{RpcManager}} method doesn't exist yet) and save the entries in the context in the {{ResponseCollector}} implementation. Multiple invocations could also share the same collector, but then you have to somehow cancel the collector after the first exception. Or you could cache the exception in the collector, and only throw it after you got a reply from all the targets... -- This message was sent by Atlassian JIRA (v7.2.3#72005)