[ https://issues.jboss.org/browse/ISPN-9206?page=com.atlassian.jira.plugin.... ] Radim Vansa commented on ISPN-9206: ----------------------------------- Conflict can be detected locally - you have all the entities that are locally available listed. If there's another node with a list that includes conflicts, it will see the conflict and won't boot. The only situation when you don't detect it (if I am not mistaken) is when you have node1 with deployments A+B, node2 with B+C and there's a conflict between A and C. I consider hashcodes on by default a safe choice: turning that off is a workaround because the situation might theoretically arise. -- This message was sent by Atlassian JIRA (v7.5.0#75005)