I will Share my Point

Question: How to build a barrier like a a traffic light for threads and synchronize them? Solution: That's what brought us to the barrier of  framework 4 ! I built code that gets three threads and trying to sync. There are three types of situations: 1. Green - do not get their delayed and continue normal (driving). 2. Yellow - paused for a second and then goes through the green . 3. Red - delayed for 2 seconds and then goes through the yellow color. The following code shows a good example of a barrier. Sync object is a barrier. It causes delay by type situation. Join activates the trigger of the action ( TrafficLightsAction ). using  System; using  System.Collections.Generic; using  System.Linq; using  System.Text; using  System.Threading; using  System.Threading.Tasks; namespace  BarrierTrafficLights {       class   Program      {    ...

This time I came across a seemingly simple problem I received the following message at the portal Server is too busy CPU processor of Windows SharePoint Server yield was 100% !!! CPU 100% Thanks to RRaveen - How to resolve the “Server Too Busy” error in asp.net , I understand what the problem. Previously explained how to solve a problem of " large data transfer in web service " I showed how to change executionTimeout on the web.config To correct the error - You need to change the variable " executionTimeout " to 3600 (this an hour because it a number of seconds - 60 * 60 = 3600) Go to the web.config and set the tag httpRuntime the following code on the " system.web " tag. < system.web >   < httpRuntime executionTimeout = " 3600 " maxRequestLength = " 51200 " > ... This should solve the problem. If not, Should reduce the number (the default is 110 seconds). thanks, Roi