IOHandler.ReadTimeout

[BartKindt]

By default the (Client) IOHandler.ReadTimeout is set to -1.

What does this mean if it is not changed?  Is it internally setting another default, or wil it not time out at all, and keep waiting?

I have a situation where a ReadTimeout occurs all the time with the default settings, and the Client loops. I have no idea after how much time it actually times out.

Bart

[rlebeau]

By default the (Client) IOHandler.ReadTimeout is set to -1.

That is IdTimeoutDefault.

What does this mean if it is not changed?  Is it internally setting another default, or wil it not time out at all, and keep waiting?

If ReadTimeout is set to IdTimeoutDefault then IdTimeoutInfinite will be used.

I have a situation where a ReadTimeout occurs all the time with the default settings, and the Client loops.

Are you performing a read operation that ignores the ReadTimeout, such as CheckForDataOnSource()? Can you show the actual code you are having trouble with?

[BartKindt]

I now see in the debug log that it times out after 10 seconds. I did not set that, but there is nothing wrong with such a long period. I am working with this specific customer why it is happening, it affects all computers on their LAN. I was thinking firewall, but it must be LAN related as no other clients connected to my Internet server have problems. I just was confused by the -1 default, but I now see that it is using 10 seconds, which is fine by me.

Thanks Remy,
Bart