https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-713 controller <p>Steps to reproduce<br/> -------------------<br/> 1. Start a single controller node with clustering enabled<br/> 2. Connect mininet to the controller<br/> 3. On the controller console press CTRL+C to exit<br/> 4. Exit mininet<br/> 5. Start the controller again</p> <p>You will see the following exception show up.</p> <p>2014-08-19 21:59:02 PDT <span class="error">&#91;com.google.common.util.concurrent.Futures$ImmediateFuture&#93;</span> SEVERE com.google.common.util.concurrent.Futures$ImmediateFuture addListener RuntimeException while executing runnable com.google.common.util.concurrent.Futures$4@6d11edc3 with executor com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService@3410d526<br/> java.lang.NullPointerException<br/> at org.opendaylight.controller.cluster.datastore.Shard$2.onSuccess(Shard.java:273)<br/> at org.opendaylight.controller.cluster.datastore.Shard$2.onSuccess(Shard.java:271)<br/> at com.google.common.util.concurrent.Futures$4.run(Futures.java:1149)<br/> at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:293)<br/> at com.google.common.util.concurrent.Futures$ImmediateFuture.addListener(Futures.java:99)<br/> at com.google.common.util.concurrent.Futures.addCallback(Futures.java:1152)<br/> at com.google.common.util.concurrent.Futures.addCallback(Futures.java:1088)<br/> at org.opendaylight.controller.cluster.datastore.Shard.commit(Shard.java:271)<br/> at org.opendaylight.controller.cluster.datastore.Shard.applyState(Shard.java:369)<br/> at org.opendaylight.controller.cluster.raft.RaftActor.onReceiveCommand(RaftActor.java:163)</p> <p>Operating System: Mac OS<br/> Platform: PC</p> CONTROLLER-713

Clustering : NPE on startup

Bug Resolved Done Moiz Raja Moiz Raja Wed, 20 Aug 2014 22:56:38 +0000 Fri, 5 Sep 2014 06:09:16 +0000 Fri, 5 Sep 2014 06:09:16 +0000 Helium mdsal 0 4 <p>One possible reason for this is that the initial transaction that is done by the topology manager matches the entry from the recovery log due to which a cohort is found in the map that the shard maintains. </p> <p>A possible fix may be to add a timestamp to each modification to distinguish it from the other.</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/10512/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/10512/</a></p> Duplicate CONTROLLER-712 Development External issue ID 1595 External issue URL ODL SR Target Milestone Priority Rank 0|i02m3j: