Need help with Web Services / ASP.NET 2.0

[cider123]

I have a working Web Service that runs on .NET 2.0 Framework.

Just for tracking purposes, I log a reference in SQL Server whenever an
instance fires up.

I have a Window Service that launches multiple instances of the Web
Service in Async mode.

As I move forward in testing, I slowly increase the depth and expand.

The problem I've run into is regardless of how many instances I tell it
to launch, it caps at 2. When those 2 shut down, 2 more fire up on the
next revolution of the engine cycle.

This might be a Web Server setting, or a web.config profile I'm not
familiar with. I searched around newsgroups and the web, but I feel
it's a unique setting and haven't had any luck.

How do you allow more than 2 instances?

[cider123]

Well, I've run across this now..

Here is a quotation from HTTP/1.1 spec
(chapter "8.1.4 Practical Considerations"):

"...Clients that use persistent connections SHOULD limit the number of
simultaneous connections that they maintain to a given server. A
single-user client SHOULD NOT maintain more than 2 connections with
any server or proxy. A proxy SHOULD use up to 2*N connections to
another server or proxy, where N is the number of simultaneously
active users. These guidelines are intended to improve HTTP response
times and avoid congestion."

I'm not sure if things have changed since that original spec though,
considering the design and technology and the way we've moved forward
in the past few years. An alternative would be to install multiple
instances of the Web Service and then handle the Queue process for
which ones to call, if others are already running.

Still trying to find a way to run more than 2 concurrent sessions with
just 1 Application, because if you run 2 separate Applications you can
run up to 4 concurrent instances.

[cider123]

Found a solution, maybe.. more info can be found at the blog at
http://blogs.msdn.com/darrenj/archiv...07/386655.aspx