Execution and Request timeouts

[millems]

Execution and request timeouts are currently exposed on the client configuration override object, but don't actually work. This functionality should be fixed.

[tddmonkey]

Is there any update on this? While doing fault tolerance testing I noticed that the timeouts work correctly on the sync clients but not on the async clients. This will be a blocker for going to production.

[millems]

@tddmonkey Would being able to configure the socket connect and read timeouts be sufficient to unblock you?

[tddmonkey]

@millems I'm using Reactor around all my code so pushing a .timeout() on to there was sufficient for now. It will be a pain moving forward as:

a) I have to remember to do this!
b) Timeouts will be configured in 2 places (on the actual call and also on the non-functioning config).

[alvaroc1]

Step Functions' client is unusable without being able to set the request timeout. All requests for GetActivityTask timeout before the server can close the connection (long-polling).

@millems How do you configure read timeouts?

[millems]

The read timeout can be configured in the HTTP client. For sync clients, that would be the ApacheHttpConfigurationFactory:

ApacheSdkHttpClientFactory apacheConfig = ApacheSdkHttpClientFactory.builder()
                                                                    .connectionTimeout(Duration.ofSeconds(65))
                                                                    .maxConnections(1_000)
                                                                    .build();
SWFClient client = SWFClient.builder()
                            .httpConfiguration(c -> c.httpClientFactory(apacheConfig))
                            .build();

[zoewangg]

Implemented in #724 and #657