Bug 1327 : Fixing a few Connection handling issues 77/8777/2
authorMadhu Venugopal <mavenugo@gmail.com>
Tue, 8 Jul 2014 08:04:05 +0000 (01:04 -0700)
committerMadhu Venugopal <mavenugo@gmail.com>
Tue, 8 Jul 2014 09:53:28 +0000 (02:53 -0700)
commit10fedbc4a43601fe5e1a9a007b87cd12b6e60ca4
treed53dfcef0099fcf3a84dd54472368dd377ffbc29
parent97cdd29a18977aa13c17bb8431fa1a1600268249
Bug 1327 : Fixing a few Connection handling issues

Since the library and plugin layers are seperated out into its own OSGi bundles and the initial low-level
OVSDB connection is managed by the library layer, there are cases in which the plugin layer might become
ACTIVE at a later point in time after the actual Passive OVSDB connection is established with the Library.
Also, the ConnectionManager and higher application layers can independently be restarted.

This fix brings in the robustness in the Connection management interactions between Library, Plugin, AD-SAL
and Connection Manager NSF.

In turn this makes the printCache command to work consistently which addresses the issue raised in Bug 1327

Change-Id: Ifc004f01e0306f7e71f908c063472a0b38bb572c
Signed-off-by: Madhu Venugopal <mavenugo@gmail.com>
library/src/main/java/org/opendaylight/ovsdb/lib/OvsdbConnection.java
library/src/main/java/org/opendaylight/ovsdb/lib/impl/OvsdbConnectionService.java
plugin/src/main/java/org/opendaylight/ovsdb/plugin/Activator.java
plugin/src/main/java/org/opendaylight/ovsdb/plugin/Connection.java
plugin/src/main/java/org/opendaylight/ovsdb/plugin/ConnectionService.java
plugin/src/main/java/org/opendaylight/ovsdb/plugin/InventoryService.java