You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following two metrics will give insight into HttpClientRequest write failures:
How many times HttpClientRequest content observable returned an error.
How many times the write of HttpClientRequest on the channel failed. Currently, there is a metric on how many times writing of header failed and how many times writing of content failed. Since, these metrics are over all requests, there is no way to determine how many request writes failed.
The text was updated successfully, but these errors were encountered:
ReactiveX#248 (Connection close cancels pending writes): Now only cancelling when a pooled connection is returned to the pool.
ReactiveX#249 (`BytesInspector` does not record events for `ByteBufHolder` and `FileRegion`): Recording events for ByteBufHolder and FileRegion
ReactiveX#250 (Connection closing and content stream behavior): Send error on content stream if the request/response is not completed on server/client.
ReactiveX#251 (Metric events for Request content source error and request write failure): Added metrics
The following two metrics will give insight into
HttpClientRequest
write failures:HttpClientRequest
content observable returned an error.HttpClientRequest
on the channel failed. Currently, there is a metric on how many times writing of header failed and how many times writing of content failed. Since, these metrics are over all requests, there is no way to determine how many request writes failed.The text was updated successfully, but these errors were encountered: