Deadlock when writing same nodes in different order using separate threads

It is possible for multiple threads to deadlock after concurrently create a session, modify several nodes, and save the session. For example, assume that two nodes, A and B, exist. Then if thread 1 sets a property on A then a property on B, while thread 2 uses its session to set a property on B then a property on A, the two threads will deadlock. If Infinispan is configured with deadlock detection, then after the configured amount of time (e.g., 10 seconds is the default) one of the threads will fail with a org.infinispan.util.concurrent.TimeoutException while the other may succeed.