SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/tmp/r/ch/qos/logback/logback-classic/1.2.13/logback-classic-1.2.13.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/tmp/r/org/slf4j/slf4j-simple/1.7.32/slf4j-simple-1.7.32.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
14:08:02,221 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback-test.xml] at [file:/w/workspace/bgpcep-maven-merge-0.19.x/bgp/topology-provider/target/test-classes/logback-test.xml]
14:08:02,221 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback-test.xml] occurs multiple times on the classpath.
14:08:02,221 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback-test.xml] occurs at [jar:file:/tmp/r/org/opendaylight/bgpcep/bgp-rib-impl/0.19.10-SNAPSHOT/bgp-rib-impl-0.19.10-SNAPSHOT-tests.jar!/logback-test.xml]
14:08:02,221 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback-test.xml] occurs at [jar:file:/tmp/r/org/opendaylight/yangtools/mockito-configuration/10.0.13/mockito-configuration-10.0.13.jar!/logback-test.xml]
14:08:02,221 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback-test.xml] occurs at [file:/w/workspace/bgpcep-maven-merge-0.19.x/bgp/topology-provider/target/test-classes/logback-test.xml]
14:08:02,294 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
14:08:02,302 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
14:08:02,307 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]
14:08:02,314 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
14:08:02,393 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [org.opendaylight.protocol] to false
14:08:02,393 |-INFO in ch.qos.logback.classic.joran.action.LevelAction - org.opendaylight.protocol level set to DEBUG
14:08:02,393 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[org.opendaylight.protocol]
14:08:02,394 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [org.opendaylight.bgpcep] to false
14:08:02,394 |-INFO in ch.qos.logback.classic.joran.action.LevelAction - org.opendaylight.bgpcep level set to DEBUG
14:08:02,394 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[org.opendaylight.bgpcep]
14:08:02,394 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO
14:08:02,394 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[ROOT]
14:08:02,394 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
14:08:02,396 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@38eb2c50 - Registering current configuration as safe fallback point

SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
14:08:04.977 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp:route:target:constrain?revision=2018-06-18)segments does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:bgp-message?revision=2020-01-20)bgp-message}]:142:17]
14:08:04.982 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp:route:target:constrain?revision=2018-06-18)communities does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:bgp-message?revision=2020-01-20)bgp-message}]:166:13]
14:08:04.983 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp:route:target:constrain?revision=2018-06-18)extended-communities does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:bgp-message?revision=2020-01-20)bgp-message}]:169:13]
14:08:04.984 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp:route:target:constrain?revision=2018-06-18)bgp-prefix-sid-tlvs does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:bgp-message?revision=2020-01-20)bgp-message}]:207:17]
14:08:05.000 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)sr-adj-ids does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)bgp-linkstate}]:610:9]
14:08:05.001 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)sr-lan-adj-ids does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)bgp-linkstate}]:613:9]
14:08:05.001 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)peer-set-sids does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)bgp-linkstate}]:626:9]
14:08:05.003 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)binding-sub-tlvs does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:bgp-segment-routing-ext?revision=2020-01-20)bgp-segment-routing}]:323:9]
14:08:05.003 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)sub-tlvs does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:bgp-segment-routing-ext?revision=2020-01-20)bgp-segment-routing}]:357:9]
14:08:05.004 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)sr-binding-sid-labels does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)bgp-linkstate}]:739:9]
14:08:05.006 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)plr does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:rsvp?revision=2015-08-20)rsvp}]:802:17]
14:08:05.006 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)plr-id does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:rsvp?revision=2015-08-20)rsvp}]:815:17]
14:08:05.006 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)avoid-node does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:rsvp?revision=2015-08-20)rsvp}]:821:17]
14:08:05.007 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)flag-container does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:rsvp?revision=2015-08-20)rsvp}]:997:9]
14:08:05.007 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)subobject-container does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:rsvp?revision=2015-08-20)rsvp}]:978:13]
14:08:05.008 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)subobject-container does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:rsvp?revision=2015-08-20)rsvp}]:526:9]
14:08:05.008 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)subobject-container does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:rsvp?revision=2015-08-20)rsvp}]:518:13]
14:08:05.009 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)exrs does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:rsvp?revision=2015-08-20)rsvp}]:660:25]
14:08:05.010 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)subobject-container does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:rsvp?revision=2015-08-20)rsvp}]:534:9]
14:08:05.014 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)subobject-container does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:rsvp?revision=2015-08-20)rsvp}]:568:13]
14:08:05.016 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp-linkstate?revision=2020-01-20)subobject-container does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at [{name=(urn:opendaylight:params:xml:ns:yang:rsvp?revision=2015-08-20)rsvp}]:601:13]
14:08:06.723 [main] DEBUG o.o.b.b.t.p.AbstractTopologyBuilder - Initiating topology builder from org.opendaylight.protocol.bgp.rib.DefaultRibReference@3644ae12 at KeyedInstanceIdentifier{targetType=interface org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.network.topology.Topology, path=[org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.NetworkTopology, org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.network.topology.Topology[key=TopologyKey{topologyId=Uri{value=test-topo}}]]}. AFI=Ipv4AddressFamily{qname=(urn:opendaylight:params:xml:ns:yang:bgp-types?revision=2020-01-20)ipv4-address-family}, SAFI=UnicastSubsequentAddressFamily{qname=(urn:opendaylight:params:xml:ns:yang:bgp-types?revision=2020-01-20)unicast-subsequent-address-family}
14:08:06.724 [main] DEBUG o.o.b.b.t.p.AbstractTopologyBuilder - Initializing transaction chain for topology org.opendaylight.bgpcep.bgp.topology.provider.Ipv4ReachabilityTopologyBuilder@1cf5e850
14:08:07.014 [main] DEBUG o.o.b.b.t.p.AbstractTopologyBuilder - Registered listener org.opendaylight.bgpcep.bgp.topology.provider.Ipv4ReachabilityTopologyBuilder@1cf5e850 on topology KeyedInstanceIdentifier{targetType=interface org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.network.topology.Topology, path=[org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.NetworkTopology, org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.network.topology.Topology[key=TopologyKey{topologyId=Uri{value=test-topo}}]]}. Timestamp=0
14:08:07.347 [main] INFO  o.o.m.b.d.codec.impl.LazyBindingMap - Using lazy population for maps larger than 1 element(s)
14:08:07.774 [main] INFO  o.o.b.b.t.p.AbstractTopologyBuilder - Shutting down builder for KeyedInstanceIdentifier{targetType=interface org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.network.topology.Topology, path=[org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.NetworkTopology, org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.network.topology.Topology[key=TopologyKey{topologyId=Uri{value=test-topo}}]]}
14:08:07.775 [main] DEBUG o.o.b.b.t.p.AbstractTopologyBuilder - Unregistered listener org.opendaylight.bgpcep.bgp.topology.provider.Ipv4ReachabilityTopologyBuilder@1cf5e850 on topology KeyedInstanceIdentifier{targetType=interface org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.network.topology.Topology, path=[org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.NetworkTopology, org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.network.topology.Topology[key=TopologyKey{topologyId=Uri{value=test-topo}}]]}
14:08:07.778 [main] DEBUG o.o.b.b.t.p.AbstractTopologyBuilder - Destroy transaction chain for topology org.opendaylight.bgpcep.bgp.topology.provider.Ipv4ReachabilityTopologyBuilder@1cf5e850