Hung socket on server failure


i have application running on server tcp socket connection server b. if server b goes off line (network cable pull, simulated failure, power cable pull), expect application running on server receive i/o exception, notifying application wrong.

if 2 applications run on host servers, expected behavior (i/o exception) happens within few seconds every time. when run them in operating systems hosted in hyper-v, (i hate "sometimes") exception isn't thrown several minutes, other times patience runs out (typically after 10 minutes or so) before exception fires.

has seen or heard of this? pointers? in advance!



Windows Server  >  Hyper-V



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file