This problem generaly comes from architecture issue. Openflow Lithium plugin was basicaly designed without cluster.

In this context we are able to see a missing relationship between Transaction Chain (Distributed DataStore) and Role Context (especially OpenflowOwnershipListener). Actual implementation ignores fact that only MASTER should have active TransactionChain and only MASTER should write data to DataStore (in close scenario we have to be the last one who could clean Node from DataStore and that event has to come from Entity unregistration process).

This leads to unexpected faulty states of TxChain infrastructure and might cause connection being constantly rejected and it bring transaction submit failures due to concurent modification exception.

So solution needs architecutal redesing of TransactionChainManager lifecycle.