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/NETCONF-97 netconf <p>Put 'config,standard,region,package,kar,ssh,management,odl-integration-compatible-with-all,odl-restconf,odl-netconf-mdsal,odl-netconf-connector-all' into bootFeatures, then fire ODL up. Netconf will fail to come up.</p> <p>When debug logging was enabled around the time Netconf was expected to be up, the following fragment was spotted in the logs repeating over and over again:</p> <p> ...<br/> 2015-11-05 13:22:50,644 | DEBUG | r - ConfigPusher | bind | - - | Trying to create the platform default provider<br/> 2015-11-05 13:22:50,644 | DEBUG | r - ConfigPusher | bind | - - | Trying to load com.sun.xml.internal.bind.v2.ContextFactory<br/> 2015-11-05 13:22:50,644 | DEBUG | r - ConfigPusher | bind | - - | loaded com.sun.xml.internal.bind.v2.ContextFactory from jar:<a href="file:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75.x86_64/jre/lib/rt.jar!/com/sun/xml/internal/bind/v2/ContextFactory.class" class="external-link" target="_blank" rel="nofollow noopener">file:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75.x86_64/jre/lib/rt.jar!/com/sun/xml/internal/bind/v2/ContextFactory.class</a><br/> 2015-11-05 13:22:50,644 | DEBUG | r - ConfigPusher | ContextFactory | - - | Property com.sun.xml.internal.bind.XmlAccessorFactoryis not active. Using JAXB's implementation<br/> 2015-11-05 13:22:50,645 | DEBUG | r - ConfigPusher | OptimizedAccessorFactory | - - | Using optimized Accessor for public java.util.SortedSet org.opendaylight.controller.config.persist.storage.file.xml.model.ConfigSnapshot.getCapabilities() and public void org.opendaylight.controller.config.persist.storage.file.xml.model.ConfigSnapshot.setCapabilities(java.util.SortedSet)<br/> 2015-11-05 13:22:50,646 | DEBUG | r - ConfigPusher | OptimizedAccessorFactory | - - | Using optimized Accessor for public java.lang.String org.opendaylight.controller.config.persist.storage.file.xml.model.ConfigSnapshot.getConfigSnapshot() and public void org.opendaylight.controller.config.persist.storage.file.xml.model.ConfigSnapshot.setConfigSnapshot(java.lang.String)<br/> 2015-11-05 13:22:50,646 | DEBUG | r - ConfigPusher | OptimizedAccessorFactory | - - | Using optimized Accessor for public java.util.Set org.opendaylight.controller.config.persist.storage.file.xml.model.ConfigSnapshot.getFeatures() and public void org.opendaylight.controller.config.persist.storage.file.xml.model.ConfigSnapshot.setFeatures(java.util.Set)<br/> 2015-11-05 13:22:50,648 | DEBUG | r - ConfigPusher | bind | - - | Trying to locate org/opendaylight/controller/config/persist/storage/file/xml/model/jaxb.properties<br/> 2015-11-05 13:22:50,648 | DEBUG | r - ConfigPusher | bind | - - | not found<br/> 2015-11-05 13:22:50,648 | DEBUG | r - ConfigPusher | bind | - - | Checking system property javax.xml.bind.JAXBContext<br/> 2015-11-05 13:22:50,648 | DEBUG | r - ConfigPusher | bind | - - | not found<br/> 2015-11-05 13:22:50,648 | DEBUG | r - ConfigPusher | bind | - - | Checking META-INF/services<br/> 2015-11-05 13:22:50,648 | DEBUG | r - ConfigPusher | bind | - - | Unable to find: META-INF/services/javax.xml.bind.JAXBContext<br/> 2015-11-05 13:22:50,648 | DEBUG | r - ConfigPusher | bind | - - | Trying to create the platform default provider<br/> ...</p> <p>(the first "Trying to create the platform default provider" at the start is from the previous iteration of the infinite loop, the last one belongs to the current iteration and is followed by another instance of the second log message which is followed by another instance of the third log message and so on and so forth).<br/> (messages from other features/subsystems are randomly interspersed).</p> <p>From my perspective this is what the logs are telling me about what is happening:</p> <p>1. "/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75.x86_64/jre/lib/rt.jar!/com/sun/xml/internal/bind/v2/ContextFactory.class" tries to access "com.sun.xml.internal.bind.XmlAccessorFactoryis"<br/> 2. Because "com.sun.xml.internal.bind.XmlAccessorFactoryis" is "not active", the code tries to load and use "JAXB's implementation"<br/> 3. The "Using JAXB's implementation" tries to access "jaxb.properties".<br/> 4. The "jaxb.properties" is discovered to be nowhere to be found.<br/> 5. Because of that, "META-INF/services/javax.xml.bind.JAXBContext" cannot be found and the code thus tries to create "the default platform provider"<br/> 6. The default platform provider is "/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75.x86_64/jre/lib/rt.jar!/com/sun/xml/internal/bind/v2/ContextFactory.class" and because of that the loop repeats.</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-97

netconf won't come up with 'odl-integration-compatible-with-all'

Bug Resolved Done Unassigned Jozef Behran Thu, 5 Nov 2015 14:48:47 +0000 Fri, 15 Mar 2019 22:22:16 +0000 Mon, 4 Jan 2016 02:26:54 +0000 netconf 0 6 <p>Occurs in stable-lithium branch:</p> <p><a href="https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-1node-userfeatures-all-stable-lithium/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-1node-userfeatures-all-stable-lithium/</a></p> <p>Right we talk about this issue every Li SR reviews, thanks for opening the bug.</p> <p>Looking at karaf.log <span class="error">&#91;0&#93;</span>, there is another symptom, visible due to workaround for <a href="https://jira.opendaylight.org/browse/CONTROLLER-1200" title="Spawning Netconf Connectors while controller is running not working" class="issue-link" data-issue-key="CONTROLLER-1200"><del>CONTROLLER-1200</del></a>. This message keeps repeating:</p> <p>2015-11-05 19:19:46,735 | WARN | r - ConfigPusher | FeatureConfigPusher | 144 - config-persister-feature-adapter - 0.3.3.SNAPSHOT | Feature: standard-condition-webconsole_0_0_0, 3.0.3 is missing from features service. Skipping</p> <p>Perhaps ConfigPushingRunnable does not detect there is nothing more to push; or (more probably) there is still something to push, but there is not enough logging to see what it is and why it does not get pushed quickly enough.</p> <p><span class="error">&#91;0&#93;</span> <a href="https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-1node-userfeatures-all-stable-lithium/lastSuccessfulBuild/artifact/karaf.log" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-1node-userfeatures-all-stable-lithium/lastSuccessfulBuild/artifact/karaf.log</a></p> <p>Manual testing shows that if all odl-sfc* features are removed from odl-integration-compatible-with-all, this Bug does not happen.<br/> More examination in progress.</p> <p>It is the<br/> &lt;configfile finalname="etc/opendaylight/karaf/sfc-netconf-initial.xml"&gt;<br/> of odl-sfc-netconf which triggers the behavior.</p> <p>But there were no changes in sfc or main netconf recently, the change which introduced failures was in fact <a href="https://git.opendaylight.org/gerrit/28985" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/28985</a></p> <p>So this seem to be a bug in config persister implementation.</p> <p>&gt; the change which introduced failures was in fact <a href="https://git.opendaylight.org/gerrit/28985" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/28985</a></p> <p>Not true. I looked at wrong job, sorry.<br/> This Lithium Bug occurred way earlier than that.</p> <p>&gt; etc/opendaylight/karaf/sfc-netconf-initial.xml</p> <p>And also this is not a real signal, just a coincidence due to my uneven patience.<br/> Both with and without this file ODL stabilizes at around the same time (12 and half minutes since started, in my environment).<br/> I still have to verify controller-netconf is mounted after that time.</p> <p>If this really turns out to be merely a bootup performance bug, perhaps this e-mail would be relevant for the fix: <a href="https://lists.opendaylight.org/pipermail/controller-dev/2015-September/010305.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/controller-dev/2015-September/010305.html</a></p> <p>Turns out my first binary search was focused on the wrong symptom. CPU stability always eventually happen, the critical symptom is whether there are data mounted on controller-config afterwards.</p> <p>My examination found a single culprit:<br/> &lt;bundle&gt;mvn:org.opendaylight.snmp4sdn/md-model/0.2.3-SNAPSHOT&lt;/bundle&gt;<br/> in other words this Bug is a consequence of <a href="https://jira.opendaylight.org/browse/SNMP4SDN-9" title="config.yang file conflict between snmp4sdn feature and controller config subsytem." class="issue-link" data-issue-key="SNMP4SDN-9"><del>SNMP4SDN-9</del></a>.</p> <p>Workaround to unblock testing without actually fixing <a href="https://jira.opendaylight.org/browse/SNMP4SDN-9" title="config.yang file conflict between snmp4sdn feature and controller config subsytem." class="issue-link" data-issue-key="SNMP4SDN-9"><del>SNMP4SDN-9</del></a> is to move snmp4sdn from odl-integration-compatble-with-all:<br/> <a href="https://git.opendaylight.org/gerrit/29671" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/29671</a> (integration/distribution Lithium)</p> <p><a href="https://jira.opendaylight.org/browse/SNMP4SDN-9" title="config.yang file conflict between snmp4sdn feature and controller config subsytem." class="issue-link" data-issue-key="SNMP4SDN-9"><del>SNMP4SDN-9</del></a> was just fixed, thanks.</p> Blocks SNMP4SDN-9 Development External issue ID 4583 External issue URL ODL SR Target Milestone Rank 0|i01wfr: