|
|
|
After setting a query timeout in ADO.NET (or any other client API), the timeout was applied to any query executed from that point on with no possibility of resetting it to 0 (infinite). A value is maintained indicating the timeout for the current operation (held connection wise). At the communication level, this value is changed for each call so that it stays current. Logic exists to calculate and update a maximum time whenever the operation requested sets a timeout different than 0. If the requested timeout was 0, this value was left unchanged, which may have caused unexpected timeouts. This was corrected by resetting the maximum to 0 when the timeout is 0.
