For some yet to be identified reason, the response coming from RA doesn't contain the payload and the client always expects to have payload. So when the client tries to decode missing payload it throws an error which makes the connection stream to stop flowing. There are few more cases where the client is throwing run time exception in side the http2 closures that causes the streams stop execution. This ticket is to track all changes to address above issues.
For some yet to be identified reason, the response coming from RA doesn't contain the payload and the client always expects to have payload. So when the client tries to decode missing payload it throws an error which makes the connection stream to stop flowing. There are few more cases where the client is throwing run time exception in side the http2 closures that causes the streams stop execution. This ticket is to track all changes to address above issues.