Vs, WCF (DOTNET) common error handling series (sorting)

1) since the previous function evaluate times out, the function evaluate is disabled. You must continue the execution to re-enable function evaluation:

This is because variables in windows such as local and watch are automatically evaluated during debugging (or the mouse stays) to prevent program errors (such as endless loops) written by users ), the system has a timeout limit. If the get operation of an attribute is complicated (instead of simply returning a private variable ), this limit may be exceeded (if strpage is large, your regular operation will probably time out ).

You can disable the automatic evaluation function:
Tools> Options> debugging> General> enable attribute evaluation and other implicit function calls
Remove the preceding check box, but the attribute variables will not be automatically evaluated.

Http://msdn.microsoft.com/en-us/library/ms234762%28VS.80%29.aspx

Http://blogs.msdn.com/greggm/archive/2004/02/04/67766.aspx

Vs.
2) restrictions on the number of IIS threads
IIS6 in any version of win2003 has restrictions on threads.
You can modify the values of maxworkerthreads and maxiothreads in Machin. config.
However, it is best not to set it too large, otherwise the CPU will waste a lot of resources in thread management.

In IIS management, locate the website node, right-click the property page, and go to the performance page. Check whether the limit is set or the number of connections is large.

If the number of connections exceeds the configured limit, the message "Service unavailable" appears. If no limit is set, the number of connections is large. When the request queue is full, the message "server too busy" appears.

Http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/a8c5b994-7722-4dc6-a246-7dfe667c6816.mspx? MFR = true

3) system. timeoutexception: The request channel times out while waiting for a reply after 00:01:00. Increase the timeout value passed to the request call, or increase the sendtimeout value on the binding.

1) First, ensure that each connection established by the client is closed after use. That is, the close () method is called,
Otherwise, the connection is automatically closed after the set session (usually 10 minutes). During this period, no client can use this service.
2) if the default number of connections does not meet the needs of the client, you can increase the number of connections. The configuration file is as follows:
<Servicethrottling maxconcurrentcils = "20" maxconcurrentsessions = "20"
Maxconcurrentinstances = "30"/>

Description: maxconcurrentcils: Maximum number of concurrent tasks. The default value is 16.

Maxconcurrentsessions: the maximum number of sessions. It is mainly used for persessions. The default value is 10.

Maxconcurrentinstances: Maximum number of instances. The default value is 26.

4) main thread and subthread issues.
Thread. Join ().
Note: In winform, if you want to continue execution after the sub-thread is completed, you cannot call the main thread method in the thread,
This will cause a deadlock in the thread call.