Timeout error (FI-1708)

[madhavdarji]

Is it possible for Inferno to list test that failed due to timeout and continue with other pre-canned tests? Below is an error we are seeing in 1 of our tests.

4.15.01 Server returns valid results for Observation search by patient + code
Error: Timed out reading data from server

/usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:751:in `rescue in transmit'

[yunwwang]

@madhavdarji

Thank you for raising this issue to us. We will add more details to the error display.

[madhavdarji]

What's the read timeout setup for single patient API?

[jpdow02]

Can you make this read timeout setting configurable? I understand the default is 60 seconds.

[yunwwang]

@jpdow02 What is the use case that a server could take more than 60 second to respond a FHIR request?

[satyaki-bhargava]

@yunwwang : As most of these FHIR servers will be test servers or mock server will have less power in terms of hardware. That is where we can use larger timeout values. However it will lead to a issue of token being expired within 59 seconds, so we are adding it, we also need to think of getting token refreshed for a given test case.

[yunwwang]

"As most of these FHIR servers will be test servers or mock server will have less power in terms of hardware."
I am not sure if this is true. That also means server implementer has options to boost server performance.

If you do need an exception due to server limitation, please work with your proctor to figure out what your options are.

[yunwwang]

Recategorize this issue. Inferno will provide a better test error message instead of the purple error as shown in the screen shot

[MCoderIndia]

We have observed that the following socket error:

In this client socket timeout error, not sure, please look into it, as it seems related to the same issues hence adding here. Please let me know if need to create new issue. Observation the socket closed once 1000 resources have been read.