SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/tmp/r/ch/qos/logback/logback-classic/1.2.12/logback-classic-1.2.12.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.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
14:13:56.057 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp:test?revision=2018-05-15)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:13:56.061 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp:test?revision=2018-05-15)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:13:56.063 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp:test?revision=2018-05-15)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:13:56.064 [main] INFO  o.o.y.y.p.r.s.l.ListStatementSupport - Configuration list (urn:opendaylight:params:xml:ns:yang:bgp:test?revision=2018-05-15)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:13:56.986 [main] INFO  o.o.p.b.b.app.AppPeerBenchmark - BGP Application Peer Benchmark Application started.
14:13:56.986 [main] DEBUG o.o.p.b.b.app.AppPeerBenchmark - Instantiating App Peer Benchmark : app-peer
14:13:57.354 [pool-5-thread-1] INFO  o.o.p.b.b.app.AppPeerBenchmark - Empty Structure created for Application Peer Benchmark app-peer
14:13:57.449 [main] INFO  o.o.m.b.d.codec.impl.LazyBindingMap - Using lazy population for maps larger than 1 element(s)
14:13:57.454 [main] DEBUG o.o.p.b.b.app.AppPeerBenchmark - DatastoreBaAbstractWrite closed successfully, chain org.opendaylight.mdsal.binding.dom.adapter.BindingDOMTransactionChainAdapter@a355b
14:13:57.454 [main] INFO  o.o.p.b.b.app.AppPeerBenchmark - BGP Application Peer Benchmark Application closed.