Bryce Anderson 3ebc946c35 Log expected STREAM_CLOSED exceptions for already closed streams at DEBUG level (#9798) ... Motivation: There is an intrinsic race between a local session resetting a stream and the peer no longer sending any frames. This can result in the session receiving frames for a stream that the local peer no longer tracks. This results in a StreamException being thrown which triggers a RST_STREAM frame, which is a good thing, but also logging at level WARN, which is noisy for an expected and benign condition. Modification: Change the log level to DEBUG when logging stream errors with code STREAM_CLOSED. All others are more interesting and will continue to be logged at level WARN. Additionally, it was found that DATA frames for streams that could not have existed only resulted in a StreamException when the spec is clear that such a situation should be fatal to the connection, resulting in a GOAWAY(PROTOCOL_ERROR). Fixes #8025.		2019-11-25 09:02:55 +01:00
..
src	Log expected STREAM_CLOSED exceptions for already closed streams at DEBUG level (#9798)	2019-11-25 09:02:55 +01:00
pom.xml	Remove duplicated declaration of dependency	2019-01-21 11:54:55 +01:00