Le lundi 10 juillet 2017, Michael Vorburger <vorbur...@redhat.com> a écrit :

> On Mon, Jul 10, 2017 at 12:53 PM, Abdelmuhaimen Seaudi <asea...@gmail.com
> <javascript:_e(%7B%7D,'cvml','asea...@gmail.com');>> wrote:
>
>> Hi,
>>
>> When I try to mount Junos 17.2 in ODL, Java process experiences very high
>> CPU utilization and I see the following logs in karaf.
>>
>> What is the meaning of "Unexpected response to get-schema, expected
>> response with one child (urn:ietf:params:xml:ns:yang:i
>> etf-netconf-monitoring?revision=2010-10-04)data, but was
>> ImmutableContainerNode{nodeIdentifier=(urn:ietf:params:xml:
>> ns:yang:ietf-netconf-monitoring?revision=2010-10-04)output, value=[],
>> attributes={()message-id=m-61}}" ?
>>
>> 2017-07-09 18:46:29,850 | WARN  | oupCloseable-3-6 |
>> NetconfXMLToMessageDecoder       | 124 - org.opendaylight.netconf.netty-util
>> - 1.1.3.Boron-SR3 | XML message with unwanted leading bytes detected.
>> Discarded the 1 leading byte(s): '0a'
>>
>
> I'm no expert in this area, but this sounds like the XML sent by that
> device perhaps starts with an empty new line? NB 0a is LF... that's
> considered invalid - and some XML parser in ODL chokes on that.
>

Actually ODL detects the trailing characters and discards it, it doesn't
choke on that ;)


>
>
> Tx,
>
M.
> --
> Michael Vorburger, Red Hat
> vorbur...@redhat.com
> <javascript:_e(%7B%7D,'cvml','vorbur...@redhat.com');> | IRC: vorburger
> @freenode | ~ = http://vorburger.ch
>
>
>> 2017-07-09 18:46:29,855 | DEBUG | oupCloseable-3-6 |
>> AbstractProtocolSession          | 84 - 
>> org.opendaylight.controller.protocol-framework
>> - 0.8.3.Boron-SR3 | Message was received: <rpc-reply
>> xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:junos="
>> http://xml.juniper.net/junos/17.2R1/junos"; message-id="m-61">
>> ...cut...
>>
>> 2017-07-09 18:46:29,855 | DEBUG | oupCloseable-3-6 |
>> AbstractNetconfSession           | 124 - org.opendaylight.netconf.netty-util
>> - 1.1.3.Boron-SR3 | handling incoming message
>>
>> 2017-07-09 18:46:29,858 | DEBUG | oupCloseable-3-6 |
>> NetconfDeviceCommunicator        | 289 - 
>> org.opendaylight.netconf.sal-netconf-connector
>> - 1.4.3.Boron-SR3 | RemoteDevice{R1}: Message received <rpc-reply
>> xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:junos="
>> http://xml.juniper.net/junos/17.2R1/junos"; message-id="m-61">
>> ...cut...
>>
>> 2017-07-09 18:46:29,859 | DEBUG | oupCloseable-3-6 |
>> AbstractSchemaRepository         | 87 - 
>> org.opendaylight.yangtools.yang-model-util
>> - 1.0.3.Boron-SR3 | Failed to acquire source from
>> AbstractObjectRegistration{instance=org.opendaylight.yangtoo
>> ls.yang.model.repo.spi.PotentialSchemaSource@10147885}
>> java.lang.IllegalStateException: RemoteDevice{R1} Unexpected response to
>> get-schema, expected response with one child (urn:ietf:params:xml:ns:yang:i
>> etf-netconf-monitoring?revision=2010-10-04)data, but was
>> ImmutableContainerNode{nodeIdentifier=(urn:ietf:params:xml:
>> ns:yang:ietf-netconf-monitoring?revision=2010-10-04)output, value=[],
>> attributes={()message-id=m-61}}
>>
>> 2017-07-09 18:46:29,859 | DEBUG | oupCloseable-3-6 |
>> AbstractSchemaRepository         | 87 - 
>> org.opendaylight.yangtools.yang-model-util
>> - 1.0.3.Boron-SR3 | Failed to acquire source from
>> AbstractObjectRegistration{instance=org.opendaylight.yangtoo
>> ls.yang.model.repo.spi.PotentialSchemaSource@5e08e193}
>> org.opendaylight.yangtools.yang.model.repo.api.MissingSchemaSourceException:
>> All available providers exhausted
>>
>>
>> Abdelmuhaimen Seaudi, CCIE # 25265
>> Email: asea...@gmail.com
>> <javascript:_e(%7B%7D,'cvml','asea...@gmail.com');>
>> Skype: aseaudi
>> LinkedIn: www.linkedin.com/in/aseaudi
>> Telephone: +2012 84644 733
>>
>>
>> _______________________________________________
>> controller-dev mailing list
>> controller-dev@lists.opendaylight.org
>> <javascript:_e(%7B%7D,'cvml','controller-dev@lists.opendaylight.org');>
>> https://lists.opendaylight.org/mailman/listinfo/controller-dev
>>
>>
>
_______________________________________________
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev

Reply via email to