Under high concurrent SSH connect load, the first data delivered on a newly opened channel can be missing its leading bytes.
Observed with ~250 concurrent NETCONF subsystem sessions. A small fraction of sessions receive a corrupt server <hello> and fail XML parsing.
Example corrupt first message:
urn:ietf:params:xml:ns:yang:iana-if-type?module=iana-if-type&revision=2014-05-08</capability><capability>urn:ietf:params:xml:ns:yang:ietf-restconf-monitoring?...
the <?xml...><hello><capabilities><capability> prefix is missing.
Under high concurrent SSH connect load, the first data delivered on a newly opened channel can be missing its leading bytes.
Observed with ~250 concurrent NETCONF subsystem sessions. A small fraction of sessions receive a corrupt server
<hello>and fail XML parsing.Example corrupt first message:
urn:ietf:params:xml:ns:yang:iana-if-type?module=iana-if-type&revision=2014-05-08</capability><capability>urn:ietf:params:xml:ns:yang:ietf-restconf-monitoring?...the
<?xml...><hello><capabilities><capability>prefix is missing.