Bug 8248: Don't access DSBE from different threads 29/55929/3
authorLorand Jakab <lojakab@cisco.com>
Mon, 24 Apr 2017 18:55:50 +0000 (21:55 +0300)
committerLorand Jakab <lojakab@cisco.com>
Tue, 25 Apr 2017 06:25:55 +0000 (09:25 +0300)
commit4abb837c8b5b90cfa1b1f14b21316fc0320b663c
tree206988c0dc5db6d90dbdc00f0cb0fe6bd815ea37
parentde15bf202fb49fe826d549bf88c5c6170f73087a
Bug 8248: Don't access DSBE from different threads

With Epoll we may have more than one LispSouthboundHandler thread, and
they may access the same DataStoreBackEnd (DSBE) instance concurrently.
This patch moves DSBE access to the single threaded
LispSouthboundPlugin. Additionally, it implements some suggestions from
the following thread:

https://lists.opendaylight.org/pipermail/release/2017-April/010273.html

Change-Id: I32f48b6dcb58b241a4a679f7145bd36b5f410861
Signed-off-by: Lorand Jakab <lojakab@cisco.com>
mappingservice/dsbackend/src/main/java/org/opendaylight/lispflowmapping/dsbackend/DataStoreBackEnd.java
mappingservice/southbound/src/main/java/org/opendaylight/lispflowmapping/southbound/LispSouthboundPlugin.java
mappingservice/southbound/src/main/java/org/opendaylight/lispflowmapping/southbound/lisp/LispSouthboundHandler.java
mappingservice/southbound/src/test/java/org/opendaylight/lispflowmapping/southbound/LispSouthboundPluginTest.java
mappingservice/southbound/src/test/java/org/opendaylight/lispflowmapping/southbound/lisp/LispSouthboundServiceTest.java