My application (Windows, VA 7.5) is running an XML WSI server. Processing of some XML requests can take very long.
Now if processing takes more than 120 seconds, it seems that the connection is dropped due to some timeout. The client application then gets the socket error 10054 ("Connection reset by peer").
cknittel wrote:Hi Marten,
Yes, it happens in a local network. It even happens when the server and the client application run on the same machine.
I am sure that the port is not closed immediately because everything works fine for processing times < 120 seconds.
cknittel wrote:According to http://support.microsoft.com/kb/923200, the timeout for the FIN_WAIT_2 state can be changed in the registry (at least in Windows Server 2003), but on my XP machine this had no effect.
marten wrote:cknittel wrote:
2.) Then it closes the sending half of its connection immediately
I do not understand this point ...
Users browsing this forum: Yahoo [Bot] and 1 guest