Re: Socket Server getting 'hung' & how to diagnose

[David Gibbs <david@xxxxxxxxxxxx>]

Scott Klement wrote:
> One of the aggravating things about communications programs is that 
> there's so much that can go wrong in a communications link.  It's nearly 
> impossible to go through a testing process that will create every 
> possible failure that could happen.  It's hard to replicate 
> communications errors in a test environment!

Not only that, but it's very hard to identify WHERE the failure is occurring.

I've had many situations where the customer SWEARS that there have been no changes to their networking infrastructure ... but all of a sudden our comms programs stop working for no apparent reason.

After digging for quite a while (including putting debuggable code on the customers system and debugging remotely) it's identified that something did change in the networking infrastructure.  Some router was tweaked, or a firewall rule updated, etc.

david