Make sure TransactionInvokerImpl chain is properly protected 80/86280/15
authorRobert Varga <robert.varga@pantheon.tech>
Fri, 6 Dec 2019 21:08:28 +0000 (22:08 +0100)
committerStephen Kitt <skitt@redhat.com>
Tue, 7 Jan 2020 16:04:52 +0000 (16:04 +0000)
commit376e7f96fffb239a1bc1647a17f9e4fe9b909f5a
tree32271776f8cba9f360fd317820e7f19030b2b126
parentf44fb67ea29af16f7123d8d709632d6d6707949d
Make sure TransactionInvokerImpl chain is properly protected

TransactionChains require single-threaded access, most notably
their close() contract requires that there be no outstanding
transactions.

There is a slight possibility of us violating this contract by
invoking close() while there is some command processing going
on.

Make sure we are properly synchronized when invoking the close()
call.

Change-Id: Idacc7096af448dc3a935ca3aa7ea2452bbd0135e
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/transactions/md/TransactionInvokerImpl.java