When node disconnects from master controller, no node takes over 88/5588/2
authorYevgeny Khodorkovsky <ykhodork@cisco.com>
Tue, 11 Mar 2014 02:15:42 +0000 (19:15 -0700)
committerYevgeny Khodorkovsky <ykhodork@cisco.com>
Tue, 11 Mar 2014 02:54:03 +0000 (19:54 -0700)
commit78405e6699eb9c85e8b0c3e2fd85a798f0bcbd55
treef01a4d5a485680486a8fb9411cef23d7b0a71b84
parent3037a8b4158f8e4dbb891047180c5b1a9a0e053b
When node disconnects from master controller, no node takes over

- Node connections caches in connection manager were allocated after
  configureInstance call, thus failing CacheUpdateAware registration.

- Fix couple of NPEs in devices.web

Change-Id: I51975a4a984606ecfad8db0941315164eedc83cb
Signed-off-by: Yevgeny Khodorkovsky <ykhodork@cisco.com>
opendaylight/clustering/services_implementation/src/main/java/org/opendaylight/controller/clustering/services_implementation/internal/ClusterGlobalManager.java
opendaylight/clustering/services_implementation/src/main/java/org/opendaylight/controller/clustering/services_implementation/internal/ClusterManagerCommon.java
opendaylight/connectionmanager/implementation/src/main/java/org/opendaylight/controller/connectionmanager/internal/ConnectionManager.java
opendaylight/connectionmanager/implementation/src/main/java/org/opendaylight/controller/connectionmanager/scheme/AbstractScheme.java
opendaylight/web/devices/src/main/java/org/opendaylight/controller/devices/web/Devices.java