TcpChannel timeout in remoting

This has been a frequently asked question about whether there is timeout support on remoting tcp channel. In 2.0 we have added support for timeouts. Unfortunately the support is missing in beta2 -- but should be available when 2.0 is released. The configuration is similar to the HTTP channel. Note that this timeout only affects read / write from native sockets. Connect timeout is not controlled via this setting. Also note that the timeout would be approximate and not a method level but a channel level setting.

Comments (1)

  1. LittleColin says:

    I know this is really old now but do you know if the *connect* timeout can be controlled and if so, how?

Skip to main content