@surendarchandra wrote:
We’re using HTTP2. When there are multiple GETs a few POSTs,we sometimes run into a scenario where a POST gets stuck waiting for entity for over 30 seconds. Since I’ve configured the limit to be 30 seconds, it triggers a HTTP 408 error for that POST request which unfreezees the rest of the pipeline. I don’t think 30 sconds is too low, it feels like I’m running out of threads to process this entity and some how the timeout frees up some thread for the other POST messages (which doesn’t make sense). Any ideas? Thanks much
Posts: 1
Participants: 1