Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
tsql:detecting_rpc_timeouts [2014/11/27 22:38]
127.0.0.1 external edit
tsql:detecting_rpc_timeouts [2017/07/21 21:47] (current)
Line 9: Line 9:
  
 ===== Workaround ===== ===== Workaround =====
-When an RPC call times out, no response code is returned (effectively ​a ''​NULL'' ​is returned). By creating and assigning a local variable to which the RPC response code is subsequently assigned, you can detect circumstances in which a ''​NULL'' ​response code is returned:+When an RPC call times out, //no// return status ​is produced, as if a ''​NULL'' ​was returned ​(assigning the return status to an already-assigned variable will remove the contents of that variable). By creating and assigning a local variable to which the RPC return status ​is subsequently assigned, you can detect circumstances in which a ''​NULL'' ​return status ​is returned:
  
 <code tsql>​DECLARE @ret INT = 123 <code tsql>​DECLARE @ret INT = 123
Line 19: Line 19:
    
 <WRAP center round important 80%> <WRAP center round important 80%>
-Note that while the NULL response code is a symptom of a RPC timeout, it remains possible that other remote errors might behave in the same way. If you find you're detecting '​timeouts'​ that don't look like timeouts (e.g. if not enough time has elapsed for it to be a real timeout), you may want to think again…+Note that while the NULL return status ​is a symptom of a RPC timeout, it remains possible that other remote errors might behave in the same way. If you find that you're detecting '​timeouts'​ that don't look like timeouts (e.g. if not enough time has elapsed for it to be a real timeout), you may want to think again…
 </​WRAP>​ </​WRAP>​