When a NETCONF XML message is corrupted, SAXParseException is raised while parsing the XML message. In some cases, e.g. when there is an invalid character, the exception is raised before all the data in the buffer is read. And in this case the next decoding is started from the point where the parsing was aborted and this in turn will cause another parsing failure. This repeatedly happens until all the remaining data in the buffer is exhausted. If the corrupted XML message is large, then this may put significant load on the controller and generate a lot of log messages.