Select and Implement New Atrtibute Reflecting Remote Server Response Timeout (for Outbound Gateways) [INT-2263]

[spring-operator]

Gary Russell opened INT-2263 and commented

Determines how long the gateway will wait for a reply from the remote server, before throwing an exception.

Currently reply-timeout on the TcpOutboundGateway, but that attribute should be for when sending the reply after it has been received (see #6247).

---

Affects: 2.1 M3

Issue Links:

• Add reply-timeout to All Outbound Gateways [INT-2262] #6247 Add reply-timeout to All Outbound Gateways

• TCP Outbound Gateway - Reconcile reply-timeout with INT-2262 and INT-2263 [INT-2264] #6249 TCP Outbound Gateway - Reconcile reply-timeout with Add reply-timeout to All Outbound Gateways [INT-2262] #6247 and Select and Implement New Atrtibute Reflecting Remote Server Response Timeout (for Outbound Gateways) [INT-2263] #6248

• On Outbound Gateways deprecate "request-timeout" and provide "reply-timeout" across Components [INT-2248] #6230 On Outbound Gateways deprecate "request-timeout" and provide "reply-timeout" across Components
  ("supersedes")

[spring-operator]

Gary Russell commented

Need to decide on this attribute name so I can resolve #6249 in the current sprint.

Some suggestions...

remote-timeout
server-timeout
peer-timeout

This is the time that the gateway will wait to receive a response from the remote system (for async gateways, such as TCP). Other gateways, ftp, http etc use some underlying library for this kind of timeout. At some point, we may want to consider giving the ability to configure that timeout via this attribute on those endpoints, but that is not what this JIRA is for; we just need to decide on a name for the attribute.

I think I lean towards remote or peer timeout.

Thoughts?

[spring-operator]

Oleg Zhurakousky commented

remote-timeout is what I am thinking as well baswed on your explanation

[spring-operator]

Gary Russell commented

PR: #476