While performing some load testing on a web service (using Specflow), we've stumbled on a two concurrent connections limitation. Apparently, the limitation is in the HTTP/1.1 .NET client implementation, as described in here. Our solution was to set the ServicePointManager.DefaultConnectionLimit property to the number of concurrent requests we want to test, just before creating the channel.
2014-03-05
2014-03-04
How to know which SQL Server version and edition you are running
SELECT @@VERSION AS [Version]Will return something like:
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Express Edition with Advanced Services (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)Found it here.
2013-12-18
Debugging a WCF service issue
A common scenario is your web service failing, but no application errors occur (assuming that you are catching all exceptions and logging them, that is). This is what I usually try:
- Turn on ASP.NET tracing (this is particularly important if you are setting aspNetCompatibilityEnabled to "true")
- Turn on WCF logging (don't forget to turn it off!)
- Take a look at Windows Event Viewer
Subscribe to:
Posts (Atom)