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-1500 controller <p>I occasionally see YangTextSchemaContextResolver failures in my log, showing that the schema context failed to fully assemble. I find this strange since the message reports no unsatisfied imports. I have attached a karaf.log that demonstrates one such run.</p> <p>This seems like a race condition in the way config provider models are loaded from first glance.</p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-1500

Sporadic YangTextSchemaContextResolver error failing to fully assemble schema context

Bug Resolved Cannot Reproduce Unassigned Ryan Goulding Sun, 20 Mar 2016 14:00:59 +0000 Thu, 19 Oct 2017 21:26:38 +0000 Tue, 22 Mar 2016 14:16:23 +0000 Beryllium config 0 2 <p>Attachment karaf.log has been added with description: karaf.log showing spoaradic YangTextSchemaContextResolver failure</p> <p>I will also add that the controller fails to come up in a reasonable amount of time when this error is observed. It doesn't seem harmless.</p> <p>I will clarify:</p> <p>I will also add that the controller fails to come up at all. We waited over 15 minutes and still didn't see it come up.</p> <p>TLDR:<br/> Seems your JVM is corrupted, please use Java 8.</p> <p>Root stacktrace is</p> <p>Caused by: java.lang.NullPointerException<br/> at java.util.HashMap.inflateTable(HashMap.java:315)<span class="error">&#91;:1.7.0_95&#93;</span><br/> at java.util.HashMap.&lt;init&gt;(HashMap.java:296)<span class="error">&#91;:1.7.0_95&#93;</span><br/> at com.google.common.collect.Maps.difference(Maps.java:416)<br/> at com.google.common.collect.Maps.difference(Maps.java:387)<br/> at org.opendaylight.yangtools.yang.parser.spi.SubstatementValidator.validate(SubstatementValidator.java:113)<br/> at org.opendaylight.yangtools.yang.parser.stmt.rfc6020.ValueStatementImpl$Definition.onFullDefinitionDeclared(ValueStatementImpl.java:65)<br/> at org.opendaylight.yangtools.yang.parser.stmt.reactor.StatementDefinitionContext.onDeclarationFinished(StatementDefinitionContext.java:61)</p> <p>Looking through our code<br/> <a href="https://github.com/opendaylight/yangtools/blob/c652590993b1e4660d5d557868665dbfa634ed27/yang/yang-parser-impl/src/main/java/org/opendaylight/yangtools/yang/parser/spi/SubstatementValidator.java#L113" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/opendaylight/yangtools/blob/c652590993b1e4660d5d557868665dbfa634ed27/yang/yang-parser-impl/src/main/java/org/opendaylight/yangtools/yang/parser/spi/SubstatementValidator.java#L113</a></p> <p>we never pass NULL value to Maps.difference, Guava also does not pass NULL<br/> to HashMap constructor.</p> <p>If you look into HashMap from 1.7.0_95 and offending method inflateTable - <a href="http://hg.openjdk.java.net/jdk7u/jdk7u/jdk/file/3a74fee9ba00/src/share/classes/java/util/HashMap.java" class="external-link" target="_blank" rel="nofollow noopener">http://hg.openjdk.java.net/jdk7u/jdk7u/jdk/file/3a74fee9ba00/src/share/classes/java/util/HashMap.java</a></p> <p>you could see there is no way that at offending place NULL value could be available.</p> <p>I agree with Tony. I had looked at the YangTextSchemaContextResolver and it never passes a null Map. It seems that java 7u79 has a bug. I could not find the source for u79 but in an earlier update line 315 didn't match up and I didn't see where HashMap.inflateTable could generate an NPE.</p> <p>Java 8 re-implemented the HashMap ctor and removed the inflateTable method.</p> <p>Sorry it was 7u95 and I see Tony did find the source. Line 315 should not generate an NPE.</p> <p>This was seen on internal CI system w/o doing 'apt-get dist-upgrade' so it was likely due to really old linux distro with latest/greatest JRE. I have reported back to our internal team and I am fine resolving this, as it seems to have been caused by environmental issues.</p> Development External issue ID 5563 External issue URL Rank 0|i02qyf: