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-469 controller <p><a href="https://jira.opendaylight.org/browse/CONTROLLER-459" title="Netconf connector has to wait for nodes yang schema" class="issue-link" data-issue-key="CONTROLLER-459"><del>CONTROLLER-459</del></a> was fixed using workaround that gets DataProviderService from OSGi service registry. This works fine using initial config, but after controller.currentconfig.xml is created (e.g. empty commit), this is not guaranteed to work, because of ordering of module instantiation during config 2PC.</p> <p>Use config's DI mechanism instead. Also check all other md-sal components that fish for dependencies using OSGi SR.</p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-469

sal-netconf-connector fails when instantiated using currentconfig.xml

Bug Resolved Done Unassigned Tomas Olvecky Wed, 14 May 2014 14:11:11 +0000 Tue, 25 Jul 2023 08:23:45 +0000 Fri, 4 Jul 2014 08:38:56 +0000 mdsal 0 4 <p>Attachment controller.currentconfig.xml has been added with description: failing config</p> <p>trace:<br/> Caused by: java.lang.NullPointerException: A null service reference is not allowed.<br/> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.getService(BundleContextImpl.java:586) ~<span class="error">&#91;org.eclipse.osgi-3.8.1.v20120830-144521.jar:na&#93;</span><br/> at org.opendaylight.controller.config.yang.md.sal.connector.netconf.NetconfConnectorModule.createInstance(NetconfConnectorModule.java:99) ~<span class="error">&#91;na:na&#93;</span><br/> at org.opendaylight.controller.config.yang.md.sal.connector.netconf.AbstractNetconfConnectorModule.getInstance(AbstractNetconfConnectorModule.java:128) ~<span class="error">&#91;na:na&#93;</span><br/> at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) ~<span class="error">&#91;na:na&#93;</span><br/> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~<span class="error">&#91;na:1.7.0_55&#93;</span><br/> at java.lang.reflect.Method.invoke(Method.java:606) ~<span class="error">&#91;na:1.7.0_55&#93;</span><br/> at org.opendaylight.controller.config.manager.impl.dependencyresolver.DependencyResolverManager$1.handleInvocation(DependencyResolverManager.java:144) ~<span class="error">&#91;na:na&#93;</span><br/> at com.google.common.reflect.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:70) ~<span class="error">&#91;na:na&#93;</span><br/> at com.sun.proxy.$Proxy94.getInstance(Unknown Source) ~<span class="error">&#91;na:na&#93;</span><br/> at org.opendaylight.controller.config.manager.impl.ConfigTransactionControllerImpl.secondPhaseCommit(ConfigTransactionControllerImpl.java:397) ~<span class="error">&#91;na:na&#93;</span></p> <p>This is fixed in this commit proposal :<br/> <a href="https://git.opendaylight.org/gerrit/#/c/6793/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/6793/</a></p> <p>The backwards compatibility is preserved in the commit. So if the service is not injected by config-subsystem, it is retrieved from the OSGi. Backwards compatibility will be removed later (<a href="https://bugs.opendaylight.org/show_bug.cgi?id=969" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=969</a>).</p> <p>Backwards compatibility was removed. This issue is therefore fixed.</p> Blocks CONTROLLER-465 Development External issue ID 1004 External issue URL Rank 0|i02klb: