[
https://issues.apache.org/jira/browse/TS-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498811#comment-14498811
]
Bryan Call commented on TS-3519:
--------------------------------
I found the problem. The problem was with receiving and reset frame and if we
can't find the stream then it would sent a protocol error. I changed it to
that if the id is 0 return protocol error and check to see if the stream is
null.
Please review my commit.
> HTTP/2 seeing a lot of GOAWAY frames being sent
> -----------------------------------------------
>
> Key: TS-3519
> URL: https://issues.apache.org/jira/browse/TS-3519
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP/2
> Affects Versions: 5.3.0
> Reporter: Bryan Call
> Fix For: 6.0.0
>
>
> Logging GOAWAY frames in Http2ConnectionState::main_event_handler()
> {code}
> [Apr 13 22:40:29.258] Server {0x2b08e7b3a700} ERROR: Sending GOAWAY frame
> [Apr 13 22:40:29.449] Server {0x2b08e8948700} ERROR: Sending GOAWAY frame
> [Apr 13 22:40:29.591] Server {0x2b08e7e3d700} ERROR: Sending GOAWAY frame
> [Apr 13 22:40:30.197] Server {0x2b08e8645700} ERROR: Sending GOAWAY frame
> [Apr 13 22:40:30.362] Server {0x2b08e6b2a700} ERROR: Sending GOAWAY frame
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
