Request Current
in [ASP .NET]
|
From: Johan Karlsson on 30 Mar 2010 07:07 Hi! I've have an asp.net application that calls a backend service hosted in IIS using WCF. I'm having some performance issues that seems to be related to hitting the maximum number of connections. My initial question is: The Request Current counter in ASP.NET never drops to zero. It gets stuck at a minimum of 1-4. When the counter goes up to about 19-20 the application locks. It looks like its the backend service that locks up since other applications get a timeout calling other methods. Should the Request Current counter drop to zero or is it normal that it stays at 1-4? Thanks // Johan
From: Mr. Arnold on 30 Mar 2010 10:58 "Johan Karlsson" wrote: > Hi! > > I've have an asp.net application that calls a backend service hosted in IIS > using WCF. I'm having some performance issues that seems to be related to > hitting the maximum number of connections. The max number of concurrent connection to a WCF Web service is 5. > > My initial question is: > > The Request Current counter in ASP.NET never drops to zero. It gets stuck at > a minimum of 1-4. When the counter goes up to about 19-20 the application > locks. It looks like its the backend service that locks up since other > applications get a timeout calling other methods. Maybe, the WCF service aborted and the WCF client is not closing the connection due to the abort, which is leaving the connection open. > > Should the Request Current counter drop to zero or is it normal that it > stays at 1-4? > You have 5 concurrent connections that can be used at any given time with a WCF Web service. If the connection is not being closed properly by the client, then you'll if the 5 concurrent connections pretty fast.
From: Johan Karlsson on 31 Mar 2010 02:52 Hi! Thanks for you reply! Is there a way to change the number of concurrent connections? Five seems kinda limited for a large number of users. It still don't explain the Request Current counter in ASP.NET. It can be as high as 19 before the app freezes up. // Johan "Mr. Arnold" <No(a)No.com> skrev i meddelandet news:DFAC2C38-AA35-4AEF-95C2-BCBBF17113AD(a)microsoft.com... > > > "Johan Karlsson" wrote: > >> Hi! >> >> I've have an asp.net application that calls a backend service hosted in >> IIS >> using WCF. I'm having some performance issues that seems to be related to >> hitting the maximum number of connections. > > The max number of concurrent connection to a WCF Web service is 5. > >> >> My initial question is: >> >> The Request Current counter in ASP.NET never drops to zero. It gets stuck >> at >> a minimum of 1-4. When the counter goes up to about 19-20 the application >> locks. It looks like its the backend service that locks up since other >> applications get a timeout calling other methods. > > Maybe, the WCF service aborted and the WCF client is not closing the > connection due to the abort, which is leaving the connection open. > >> >> Should the Request Current counter drop to zero or is it normal that it >> stays at 1-4? >> > > You have 5 concurrent connections that can be used at any given time with > a > WCF Web service. If the connection is not being closed properly by the > client, then you'll if the 5 concurrent connections pretty fast. >
From: Allen Chen [MSFT] on 31 Mar 2010 05:27 Hi Johan, >I've have an asp.net application that calls a backend service hosted in IIS >using WCF. I'm having some performance issues that seems to be related to >hitting the maximum number of connections. >My initial question is: >The Request Current counter in ASP.NET never drops to zero. It gets stuck at >a minimum of 1-4. When the counter goes up to about 19-20 the application >locks. It looks like its the backend service that locks up since other >applications get a timeout calling other methods. >Should the Request Current counter drop to zero or is it normal that it >stays at 1-4? You may set some WCF serviceThrottling settings to see whether it works: http://msdn.microsoft.com/en-us/library/ms731379.aspx As to the Request Current counter it's normal that it's not zero however since you said the application locks definitely something is wrong. Please let me know whether the serviceThrottling can resolve this issue. Regards, Allen Chen Microsoft Online Support Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg(a)microsoft.com. ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications. Note: MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 2 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/en-us/subscriptions/aa948874.aspx ================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
From: Allen Chen [MSFT] on 2 Apr 2010 05:10
Hi Johan, >I've have an asp.net application that calls a backend service hosted in IIS >using WCF. I'm having some performance issues that seems to be related to >hitting the maximum number of connections. >My initial question is: >The Request Current counter in ASP.NET never drops to zero. It gets stuck at >a minimum of 1-4. When the counter goes up to about 19-20 the application >locks. It looks like its the backend service that locks up since other >applications get a timeout calling other methods. >Should the Request Current counter drop to zero or is it normal that it >stays at 1-4? Do you have any progress on this issue? Regards, Allen Chen Microsoft Online Support |