Thanks Evgenii, I'll add that catch block and see if it sheds any light on the issue.
The client's transaction configuration is set to Optimistic and Serializable and the transaction within the try with resources block is explicitly set to Optimistic and Serializable, which should preclude deadlock...but there does seem to be deadlock.. The servers do not have any transaction configuration set explicitly.. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
