Operating System: All
Platform: All

I created https://bugs.opendaylight.org/show_bug.cgi?id=2976 for this same issue. This issue also occurs if you restart the controller. There's actually 2 issues here. The controller restart case is indirectly caused by the feature config pusher and persistent config pusher both trying to start the modules. Having both pushers doing the same thing on startup could lead to system instability. The underlying cause is that CDS uses a static ActorSystem and thus it tries to reuse it when restarted in the same JVM instance.

I think we need to just null out static field when closed.

https://git.opendaylight.org/gerrit/19957

I've tried putting in a more comprehensive fix here. The reproduction steps I had used are,

1. Bring up controller
2. Install the netconf feature
3. Add a netconf mount
4. Restart the controller
5. Check the logs and the mbeans.

In the logs you will see an exception that you are trying to create an actor on an actor system that is terminating/terminated. In the MBeans you will see that one of the Distributed*DataStores will not be created. The system may continue to work because the IMDS may be used instead of CDS but in that case persistence will be broken.

Yes - those are the issues I saw.

(In reply to Moiz Raja from comment #3)
> I've tried putting in a more comprehensive fix here. The reproduction steps
> I had used are,
>
> 1. Bring up controller
> 2. Install the netconf feature
> 3. Add a netconf mount
> 4. Restart the controller
> 5. Check the logs and the mbeans.
>
> In the logs you will see an exception that you are trying to create an actor
> on an actor system that is terminating/terminated. In the MBeans you will
> see that one of the Distributed*DataStores will not be created. The system
> may continue to work because the IMDS may be used instead of CDS but in
> that case persistence will be broken.