i/o timeout in Response Body in a Runscope Test Step

book

Article ID: 209188

calendar_today

Updated On:

Products

BlazeMeter

Issue/Introduction

Running a GET request in a step of a BlazeMeter API Monitoring (Runscope) test, reports a 200 status but the response body contains a message similar to the following:

read tcp <IPaddress>:<port>-><IPaddress>:<port>: i/o timeout.  Please contact support [email protected]

The response time also shows up in read with a value of 4.5 minutes :

Cause

The GET request connects successfully, but did not get the full response after waiting 4.5 minutes.  This is a hardcoded timeout.  Runscope allows only this amount of time to retrieve the complete response.  If the complete response is not received within 4.5 minutes it gives up and elicits a "read tcp" "i/o timeout" message in the response body of the step.

Environment

Release : SAAS

Component : BLAZEMETER API MONITORING

Resolution

At this time these timeouts are hard-coded and cannot be tuned.  The recommendation is to submit a feature request by following the instructions in the Submitting Feature Requests (Ideas) article if you would like Product Management to consider making an improvement in this area.

Attachments