On 07/30/2016 01:13 AM, Kevin Wang wrote: > Hi Robert, > > When trying to restart the PingPong transaction chain, I find the chain > cannot be close()d gracefully. > 1. To unlock the transaction chain, I will have to submit() the chain. It is > undesirable, as it causes data inconsistence. But it can be dealt with, as > later when we restart the data listener, the whole data could be rebuilt and > thus data loss get recovered. > 2. To restart the transaction chain, I want to close the problematic chain > first then start a new chain. But I find that if I call close() on > PingPongTransactionChain, eventually the > AbstractDOMForwardedTransactionFactory will be closed. And there is no way > to reopen it when I initialize a new PingPongTransactionChain. So the only > thing I can do now is to throw away the old transaction chain directly > without closing it. I am not sure if that will cause any resource issue in > the future. >
Right, the failure reporting path seems to be broken and it is not going to be easy to fix, as the locking is a bit involved. I will take a closer look later this week. Bye, Robert
signature.asc
Description: OpenPGP digital signature
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
