CopyPastor

Detecting plagiarism made easy.

Score: 0.8609185738938288; Reported for: String similarity Open both answers

Possible Plagiarism

Plagiarized on 2018-07-27
by Gauravsa

Original Post

Original - Posted on 2009-10-22
by jfawcett



            
Present in both answers; Present only in the new answer; Present only in the old answer;

You're probably hitting a timeout. First of all, turn the keepalive back on. Second, check the timestamps on the request and reply. If there is a firewall between the sender and receiver, make sure that it isn't closing the connection because of ***idle timeout***. I've had both these problems in the past, although with generic socket programming, not DB stuff.

You're probably hitting a timeout. First of all, turn the keepalive back on. Second, check the timestamps on the request and reply. If there is a firewall between the sender and receiver, make sure that it isn't closing the connection because of idle timeout. I've had both these problems in the past, although with generic socket programming, not DB stuff.

        
Present in both answers; Present only in the new answer; Present only in the old answer;