on 2012 Feb 13 1:06 PM
Would a database client using tcp/ip recognize if the packet transmitting the commit command to the server is lost?
Request clarification before answering.
It won't recognize this particular failure, because TCP will provide packet recovery as Breck has mentioned. Assuming TCP isn't able to recover and resend the packet, the client libraries should return a communication error (-85):
Other failures for a commit should also be surfaced as an error. Ultimately, if the call making a commit returns without an error code, the commit should succeed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Probably not, because TCP provides packet recovery: http://en.wikipedia.org/wiki/Packet_loss#Packet_recovery
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The possible answers are wayyy beyond my network knowledge, but the effect of the LivenessTimeout would come into play here, methinks.
User | Count |
---|---|
87 | |
9 | |
9 | |
8 | |
6 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.