Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Combining the details found in SO and MSDN Social threads referenced by me and eol led me to these registry settings:</p> <blockquote> <p>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces{xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxx}\TcpInitialRTT</p> <p>Value Type: REG_DWORD—number</p> <p>Valid Range: 0–0xFFFF</p> <p>Default: 3 seconds</p> <p>Description: This parameter controls the initial time-out used for a TCP connection request and initial data retransmission on a per-interface basis. Use caution when tuning with this parameter because exponential backoff is used. Setting this value to larger than 3 results in much longer time-outs to nonexistent addresses.</p> </blockquote> <p>.</p> <blockquote> <p>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces{xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxx}\TcpMaxConnectRetransmissions</p> <p>Value Type: REG_DWORD—number</p> <p>Valid Range: 0–255 (decimal)</p> <p>Default: 2</p> <p>Description: This parameter determines the number of times that TCP retransmits a connect request (SYN) before aborting the attempt. The retransmission time-out is doubled with each successive retransmission in a given connect attempt. The initial time-out is controlled by the TcpInitialRtt registry value.</p> </blockquote> <p>.</p> <blockquote> <p>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces{xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxx}\TcpMaxDataRetransmissions</p> <p>Value Type: REG_DWORD—number</p> <p>Valid Range: 0–0xFFFFFFFF</p> <p>Default: 5</p> <p>Description: This parameter controls the number of times that TCP retransmits an individual data segment (not connection request segments) before aborting the connection. The retransmission time-out is doubled with each successive retransmission on a connection. It is reset when responses resume. The Retransmission Timeout (RTO) value is dynamically adjusted, using the historical measured round-trip time (Smoothed Round Trip Time, or SRTT) on each connection. The starting RTO on a new connection is controlled by the TcpInitialRtt registry value.</p> </blockquote> <p>Since the timeout value on a failed connect is doubled for each retry, the default values make the first attempt fail in 3 seconds, the second fail in 6, and the third and final attempt fail in 12 seconds, or 21 seconds total. BTW, the <em>TcpMaxDataRetransmissions</em> key has nothing to do with this, I include it for completeness and those who come later.</p> <p>None of these values are present by default, you have to add them to change them. Figuring out which interface(s) to do this on is easy, each interface has a key containing its current IP address. (There's even one for localhost.) In my own case, just setting the <em>TcpMaxConnectRetransmissions</em> to zero (0) on the VM interfaces defaults my socket timeout for them to 3 seconds, which is close enough to 2.5 to work. My load balancing works when a WCF service crashes now.</p>
    singulars
    1. This table or related slice is empty.
    1. POWCF Client ignores timeout values when service down
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMarkFisher
    1. USMarkFisher
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CONice work getting to the root cause. Some cautions to future readers: this is a low level fix that can affect other programs on the same computer. Best used when you have limited purpose machines. Also, I see some posts about this perhaps being deprecated in some newer versions of Windows. Mark, can you let us know which windows OS you're using?
      singulars
      1. PO
      1. USeol
    2. CO@eol - Sure, I'm targeting XP->7 (.NET 4), and MS KBA http://support.microsoft.com/kb/170359 says it's supported from NT. There are RFCs covering this behavior; if discontinued, MS would have to provide support for it somewhere else. (IMHO, this is a lousy way to do this in the first place.) Could you point to the posts that indicate depreciation?
      singulars
      1. PO
      1. USMarkFisher
    3. COI should have done that to begin with. I went back to get the list and found that where I had seen this said in about 4 different places, when I looked closer they were all clones/copies of just one discussion thread (http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/110271d5-5221-44b4-af14-f07f3fa01a73, two answers down.) Since just one person stated this, and I can't find any other source to corroborate, I retract my statement about possibly being deprecated.
      singulars
      1. PO
      1. USeol
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload