Broken TCP

[prad]

Hello,
On establishing TCP connections after a brief interval, one of the nodes raises the signal 'Alarm Clock' and all the other nodes either say Broken Pipe or Error Connecting: Connection Refused (after establishing the connections) and the network connections fizzle away. Can some one point out what causes this Alarm Clock Signal ?
On 'just' establishing the connections in the network, this signal is not raised. Only when info is send and rcvd the links get broken..

[RobSeace]

The app getting hit with SIGALRM must be using some alarm()-based
timeouts, I would guess... Basically, it's something it must've asked
for itself, not something that should just happen... But, I don't know
why it wouldn't be handling the SIGALRM properly, then... If it's dying
because of it, it sounds like the code is simply buggy, and not properly
implementing some timeout it's trying to use...