Forwarding for non-transactional write commands should be asynchronous ---------------------------------------------------------------------- Key: ISPN-2473 URL: https://issues.jboss.org/browse/ISPN-2473 Project: Infinispan Issue Type: Sub-task Components: State transfer Affects Versions: 5.2.0.Beta3 Reporter: Dan Berindei Assignee: Dan Berindei Priority: Critical Fix For: 5.2.0.CR1 A write command keeps a lock on the originator while doing the RPC on the actual owners, so forwarding the command back to the originator synchronously leads to a deadlock. Keeping track of the real originator for forwarded commands could allow us to avoid the deadlock, but it would be too complicated. OTOH, non-tx caches don't guarantee consistency, so we could just do the forwarding asynchronously.