May be somebody knows if there is a product that may be addressing following issue:
- On Windows 2000 Professional/XP Professional IIS (version 6.0) is limited by 10 simultaneous TCP connections. If 11'th connection comes it going to get HTTP error. - IE uses HTTP 1.1 and Keep-Alive. If IE client made a connection to IIS (and keep-alive is on) then IE will keep this connection up to ~30 sec (even if does not have any requests to send). - Each IE client makes up to 2 connections to the IIS and keeps them in cash.
So 10 simultaneous IE clients will eat up to 10 connections and 11'th user may get an error. This becomes a limitation for my WEB application.
What I am looking for is a Proxy that would not have limitation on number of incoming TCP connections (IE to Proxy), but would be aware of IIS limitation (10 connections on Professional platform) and put client's request on hold until IIS connection would become available.
I've already considered possibility of turning off keep-alive on the server side and now interested only in discussion of the option described above (Proxy).
w/o opting for unique webserver for one site -- is the following possible??
few sites setup using same time zone setting - the addition of another website requires a separate time zone -- is there a registry fix or anything to handle a unique time zone for a particular website??
The limitation is in place because you have a workstation operating system and not a server operating system. For unlimited connections, use either one of the (now discotninued) Windows 2000 Server family or the new Windows 2003 Server family.
> May be somebody knows if there is a product that may be addressing following > issue:
> - On Windows 2000 Professional/XP Professional IIS (version 6.0) is > limited by 10 simultaneous TCP connections. > If 11'th connection comes it going to get HTTP error. > - IE uses HTTP 1.1 and Keep-Alive. If IE client made a connection to IIS > (and keep-alive is on) then IE will keep this connection > up to ~30 sec (even if does not have any requests to send). > - Each IE client makes up to 2 connections to the IIS and keeps them in > cash.
> So 10 simultaneous IE clients will eat up to 10 connections and 11'th > user may get an error. This becomes a limitation for my WEB application.
> What I am looking for is a Proxy that would not have limitation on number of > incoming TCP connections (IE to Proxy), but would be aware of IIS limitation > (10 connections on Professional platform) and put client's request on hold > until IIS connection would become available.
> I've already considered possibility of turning off keep-alive on the server > side and now interested only in discussion of the option described above > (Proxy).
Thanks for your answer. I know that. I am looking for possibility to "work-around" this limitation without making customer upgrade to Server. Any suggestions?
Vladimir.
"Cari MS-MVP" <Newsgrou...@coribright.comn> wrote in message
> The limitation is in place because you have a workstation operating system > and not a server operating system. For unlimited connections, use either > one of the (now discotninued) Windows 2000 Server family or the new Windows > 2003 Server family.
> > May be somebody knows if there is a product that may be addressing > following > > issue:
> > - On Windows 2000 Professional/XP Professional IIS (version 6.0) is > > limited by 10 simultaneous TCP connections. > > If 11'th connection comes it going to get HTTP error. > > - IE uses HTTP 1.1 and Keep-Alive. If IE client made a connection to > IIS > > (and keep-alive is on) then IE will keep this connection > > up to ~30 sec (even if does not have any requests to send). > > - Each IE client makes up to 2 connections to the IIS and keeps them > in > > cash.
> > So 10 simultaneous IE clients will eat up to 10 connections and 11'th > > user may get an error. This becomes a limitation for my WEB application.
> > What I am looking for is a Proxy that would not have limitation on number > of > > incoming TCP connections (IE to Proxy), but would be aware of IIS > limitation > > (10 connections on Professional platform) and put client's request on hold > > until IIS connection would become available.
> > I've already considered possibility of turning off keep-alive on the > server > > side and now interested only in discussion of the option described above > > (Proxy).
Which part of her answer did you not understand? You can't.
----- Vladimir Petter wrote: -----
Cari,
Thanks for your answer. I know that. I am looking for possibility to "work-around" this limitation without making customer upgrade to Server. Any suggestions?
Vladimir.
"Cari MS-MVP" <Newsgrou...@coribright.comn> wrote in message news:uEA6lw0vDHA.1888@TK2MSFTNGP10.phx.gbl... > The limitation is in place because you have a workstation operating system > and not a server operating system. For unlimited connections, use either > one of the (now discotninued) Windows 2000 Server family or the new Windows > 2003 Server family. >> Cari > www.coribright.com >> "Vladimir Petter" <vlad...@hotmail.com> wrote in message > news:uTbTPg0vDHA.684@TK2MSFTNGP09.phx.gbl... >> Dear All, >>>> May be somebody knows if there is a product that may be addressing > following >> issue: >>>> - On Windows 2000 Professional/XP Professional IIS (version 6.0) is >> limited by 10 simultaneous TCP connections. >> If 11'th connection comes it going to get HTTP error. >> - IE uses HTTP 1.1 and Keep-Alive. If IE client made a connection to > IIS >> (and keep-alive is on) then IE will keep this connection >> up to ~30 sec (even if does not have any requests to send). >> - Each IE client makes up to 2 connections to the IIS and keeps them > in >> cash. >>>> So 10 simultaneous IE clients will eat up to 10 connections and 11'th >> user may get an error. This becomes a limitation for my WEB application. >>>> What I am looking for is a Proxy that would not have limitation on number > of >> incoming TCP connections (IE to Proxy), but would be aware of IIS > limitation >> (10 connections on Professional platform) and put client's request on hold >> until IIS connection would become available. >>>> I've already considered possibility of turning off keep-alive on the > server >> side and now interested only in discussion of the option described above >> (Proxy). >>>> Regards, >> Vladimir. >>>>>>>>
Why do not you read the original question more carefully before post useless answers? Once again: - I know that it is impossible to have more than 10 connections to IIS on Professional. - I am looking for a Proxy that can accept unlimited number of IE connections and serialize them to use only 10 IIS connections (client's request will be in a queue until connection to IIS would not succeed).
If you do not have answer please do not waste bandwidth.
Vladimir.
"DUH" <anonym...@discussions.microsoft.com> wrote in message
> Which part of her answer did you not understand? You can't.
> ----- Vladimir Petter wrote: -----
> Cari,
> Thanks for your answer. > I know that. I am looking for possibility to "work-around" this limitation > without making customer upgrade to Server. > Any suggestions?
> Vladimir.
> "Cari MS-MVP" <Newsgrou...@coribright.comn> wrote in message > news:uEA6lw0vDHA.1888@TK2MSFTNGP10.phx.gbl... > > The limitation is in place because you have a workstation operating system > > and not a server operating system. For unlimited connections, use either > > one of the (now discotninued) Windows 2000 Server family or the new > Windows > > 2003 Server family. > >> Cari > > www.coribright.com > >> "Vladimir Petter" <vlad...@hotmail.com> wrote in message > > news:uTbTPg0vDHA.684@TK2MSFTNGP09.phx.gbl... > >> Dear All, > >>>> May be somebody knows if there is a product that may be addressing > > following > >> issue: > >>>> - On Windows 2000 Professional/XP Professional IIS (version 6.0) is > >> limited by 10 simultaneous TCP connections. > >> If 11'th connection comes it going to get HTTP error. > >> - IE uses HTTP 1.1 and Keep-Alive. If IE client made a connection to > > IIS > >> (and keep-alive is on) then IE will keep this connection > >> up to ~30 sec (even if does not have any requests to send). > >> - Each IE client makes up to 2 connections to the IIS and keeps them > > in > >> cash. > >>>> So 10 simultaneous IE clients will eat up to 10 connections and > 11'th > >> user may get an error. This becomes a limitation for my WEB application. > >>>> What I am looking for is a Proxy that would not have limitation on > number > > of > >> incoming TCP connections (IE to Proxy), but would be aware of IIS > > limitation > >> (10 connections on Professional platform) and put client's request on > hold > >> until IIS connection would become available. > >>>> I've already considered possibility of turning off keep-alive on the > > server > >> side and now interested only in discussion of the option described above > >> (Proxy). > >>>> Regards, > >> Vladimir.
> Thanks for your answer. > I know that. I am looking for possibility to "work-around" this limitation > without making customer upgrade to Server. > Any suggestions?
Use Apache. The 10 connection limit is coded into IIS, not XP. However, there are other limitations (such as the accept connection backlog) you will run into if the site becomes popular that can only be fixed by upgrading to a server version of Windows or another OS like Linux.
>Thanks for your answer. >I know that. I am looking for possibility to "work-around" this limitation >without making customer upgrade to Server. >Any suggestions?
>Vladimir.
Vladimir,
The best you can hope for is to do this :
"If you use IIS 5.0 on Windows 2000 Professional or IIS 5.1 on Microsoft Windows XP Professional, disable HTTP keep-alives in the properties of the Web site. When you do this, a limit of 10 concurrent connections still exists, but IIS does not maintain connections for inactive users."
but you cannot get away from the 10 concurrent connection limit - its hard-coded in the 'desktop' versions of Windows 2000 and XP
The specific of my application is that it is not actually a public WEB site. It is an internal company's site that may have about 10-15 clients. Because of WinINet limitations (we are using WinInet on client extensively) we increased max number of HTTP requests to 4 so now even 2 clients eating up 8 IIS connections.
Well I think I will try to write a kind of proxy I've described.
Regards, Vladimir.
"Paul Lynch" <paul.ly...@nospam.com> wrote in message
> On Wed, 10 Dec 2003 10:35:03 -0800, "Vladimir Petter" > <vlad...@hotmail.com> wrote:
> >Cari,
> >Thanks for your answer. > >I know that. I am looking for possibility to "work-around" this limitation > >without making customer upgrade to Server. > >Any suggestions?
> >Vladimir.
> Vladimir,
> The best you can hope for is to do this :
> "If you use IIS 5.0 on Windows 2000 Professional or IIS 5.1 on > Microsoft Windows XP Professional, disable HTTP keep-alives in the > properties of the Web site. When you do this, a limit of 10 concurrent > connections still exists, but IIS does not maintain connections for > inactive users."
> but you cannot get away from the 10 concurrent connection limit - its > hard-coded in the 'desktop' versions of Windows 2000 and XP
> > Thanks for your answer. > > I know that. I am looking for possibility to "work-around" this limitation > > without making customer upgrade to Server. > > Any suggestions?
> Use Apache. The 10 connection limit is coded into IIS, not XP. However, there > are other limitations (such as the accept connection backlog) you will run into > if the site becomes popular that can only be fixed by upgrading to a server > version of Windows or another OS like Linux.
> Thanks for your answer. > I know that. I am looking for possibility to "work-around" this limitation > without making customer upgrade to Server. > Any suggestions?
> Vladimir.
> "Cari MS-MVP" <Newsgrou...@coribright.comn> wrote in message > news:uEA6lw0vDHA.1888@TK2MSFTNGP10.phx.gbl... > > The limitation is in place because you have a workstation operating system > > and not a server operating system. For unlimited connections, use either > > one of the (now discotninued) Windows 2000 Server family or the new > Windows > > 2003 Server family.
> > > May be somebody knows if there is a product that may be addressing > > following > > > issue:
> > > - On Windows 2000 Professional/XP Professional IIS (version 6.0) is > > > limited by 10 simultaneous TCP connections. > > > If 11'th connection comes it going to get HTTP error. > > > - IE uses HTTP 1.1 and Keep-Alive. If IE client made a connection to > > IIS > > > (and keep-alive is on) then IE will keep this connection > > > up to ~30 sec (even if does not have any requests to send). > > > - Each IE client makes up to 2 connections to the IIS and keeps them > > in > > > cash.
> > > So 10 simultaneous IE clients will eat up to 10 connections and > 11'th > > > user may get an error. This becomes a limitation for my WEB application.
> > > What I am looking for is a Proxy that would not have limitation on > number > > of > > > incoming TCP connections (IE to Proxy), but would be aware of IIS > > limitation > > > (10 connections on Professional platform) and put client's request on > hold > > > until IIS connection would become available.
> > > I've already considered possibility of turning off keep-alive on the > > server > > > side and now interested only in discussion of the option described above > > > (Proxy).
Thanks for reply. Good idea, but would not do in my case :(. WEB application implemented with ASPs and have to collaborate with a set of DCOM servers. Having DCOM servers on another machine may become a pain in the but especially with coming XP SP2.
Thanks, Vladimir.
"Tom Miller" <tlgalen...@chatnfiles.com> wrote in message
> > Thanks for your answer. > > I know that. I am looking for possibility to "work-around" this limitation > > without making customer upgrade to Server. > > Any suggestions?
> > Vladimir.
> > "Cari MS-MVP" <Newsgrou...@coribright.comn> wrote in message > > news:uEA6lw0vDHA.1888@TK2MSFTNGP10.phx.gbl... > > > The limitation is in place because you have a workstation operating > system > > > and not a server operating system. For unlimited connections, use > either > > > one of the (now discotninued) Windows 2000 Server family or the new > > Windows > > > 2003 Server family.
> > > > May be somebody knows if there is a product that may be addressing > > > following > > > > issue:
> > > > - On Windows 2000 Professional/XP Professional IIS (version 6.0) > is > > > > limited by 10 simultaneous TCP connections. > > > > If 11'th connection comes it going to get HTTP error. > > > > - IE uses HTTP 1.1 and Keep-Alive. If IE client made a connection > to > > > IIS > > > > (and keep-alive is on) then IE will keep this connection > > > > up to ~30 sec (even if does not have any requests to send). > > > > - Each IE client makes up to 2 connections to the IIS and keeps > them > > > in > > > > cash.
> > > > So 10 simultaneous IE clients will eat up to 10 connections and > > 11'th > > > > user may get an error. This becomes a limitation for my WEB > application.
> > > > What I am looking for is a Proxy that would not have limitation on > > number > > > of > > > > incoming TCP connections (IE to Proxy), but would be aware of IIS > > > limitation > > > > (10 connections on Professional platform) and put client's request on > > hold > > > > until IIS connection would become available.
> > > > I've already considered possibility of turning off keep-alive on the > > > server > > > > side and now interested only in discussion of the option described > above > > > > (Proxy).
>May be somebody knows if there is a product that may be addressing following >issue:
> - On Windows 2000 Professional/XP Professional IIS (version 6.0) is >limited by 10 simultaneous TCP connections. >If 11'th connection comes it going to get HTTP error. > - IE uses HTTP 1.1 and Keep-Alive. If IE client made a connection to IIS >(and keep-alive is on) then IE will keep this connection >up to ~30 sec (even if does not have any requests to send). > - Each IE client makes up to 2 connections to the IIS and keeps them in >cash.
> So 10 simultaneous IE clients will eat up to 10 connections and 11'th >user may get an error. This becomes a limitation for my WEB application.
>What I am looking for is a Proxy that would not have limitation on number of >incoming TCP connections (IE to Proxy), but would be aware of IIS limitation >(10 connections on Professional platform) and put client's request on hold >until IIS connection would become available.
You won't find that, and it may not even be possible to write your own. The limit is inherent to the operating system, not IIS itself.
>I've already considered possibility of turning off keep-alive on the server >side and now interested only in discussion of the option described above >(Proxy).
Then I'll honor your request and not tell you the options available that would work for you.
From my current study it seams to me that proxy solution should work. The limit of connections on Professional OS has nothing to do with IIS limit (10 connections). So proxy should be able handle high number of incoming connections and make sure that it does not go above 10 on IIS.
Well if there is other possibilities (except upgrade to Server) that I overlooked then I really would like to hear it out :-).
Thanks, Vladimir.
"Jeff Cochran" <jcochran.nos...@naplesgov.com> wrote in message
> On Wed, 10 Dec 2003 10:01:44 -0800, "Vladimir Petter" > <vlad...@hotmail.com> wrote:
> >Dear All,
> >May be somebody knows if there is a product that may be addressing following > >issue:
> > - On Windows 2000 Professional/XP Professional IIS (version 6.0) is > >limited by 10 simultaneous TCP connections. > >If 11'th connection comes it going to get HTTP error. > > - IE uses HTTP 1.1 and Keep-Alive. If IE client made a connection to IIS > >(and keep-alive is on) then IE will keep this connection > >up to ~30 sec (even if does not have any requests to send). > > - Each IE client makes up to 2 connections to the IIS and keeps them in > >cash.
> > So 10 simultaneous IE clients will eat up to 10 connections and 11'th > >user may get an error. This becomes a limitation for my WEB application.
> >What I am looking for is a Proxy that would not have limitation on number of > >incoming TCP connections (IE to Proxy), but would be aware of IIS limitation > >(10 connections on Professional platform) and put client's request on hold > >until IIS connection would become available.
> You won't find that, and it may not even be possible to write your > own. The limit is inherent to the operating system, not IIS itself.
> >I've already considered possibility of turning off keep-alive on the server > >side and now interested only in discussion of the option described above > >(Proxy).
> Then I'll honor your request and not tell you the options available > that would work for you.
> "If you use IIS 5.0 on Windows 2000 Professional or IIS 5.1 on > Microsoft Windows XP Professional, disable HTTP keep-alives in the > properties of the Web site. When you do this, a limit of 10 concurrent > connections still exists, but IIS does not maintain connections for > inactive users."
> but you cannot get away from the 10 concurrent connection limit - its > hard-coded in the 'desktop' versions of Windows 2000 and XP
Just to clarify this statement... The 10 concurrent connection limit is 'hard coded' into IIS, not into XP. Even Windows 95 can have over 200 active TCP connections with other server software.
> Thanks for response. > Could you please point me to any resources telling about "connection > backlog"?
Basically, the connection backlog determines how fast clients can connect. In other words, if too many clients request a connect at about the same time, the connection backlog fills up and some will be rejected. You would need to see more than a few hundred connections per second before this would become a problem.
Jeff Cochran wrote: > On Wed, 10 Dec 2003 10:01:44 -0800, "Vladimir Petter" > <vlad...@hotmail.com> wrote:
>>Dear All,
>>May be somebody knows if there is a product that may be addressing following >>issue:
>> - On Windows 2000 Professional/XP Professional IIS (version 6.0) is >>limited by 10 simultaneous TCP connections. >>If 11'th connection comes it going to get HTTP error. >> - IE uses HTTP 1.1 and Keep-Alive. If IE client made a connection to IIS >>(and keep-alive is on) then IE will keep this connection >>up to ~30 sec (even if does not have any requests to send). >> - Each IE client makes up to 2 connections to the IIS and keeps them in >>cash.
>> So 10 simultaneous IE clients will eat up to 10 connections and 11'th >>user may get an error. This becomes a limitation for my WEB application.
>>What I am looking for is a Proxy that would not have limitation on number of >>incoming TCP connections (IE to Proxy), but would be aware of IIS limitation >>(10 connections on Professional platform) and put client's request on hold >>until IIS connection would become available.
> You won't find that, and it may not even be possible to write your > own. The limit is inherent to the operating system, not IIS itself.
That is false. The limit is coded into IIS. I have accepted more than 8000 simultaneous TCP connections on Windows 2000 and XP Pro.
>>I've already considered possibility of turning off keep-alive on the server >>side and now interested only in discussion of the option described above >>(Proxy).
> Then I'll honor your request and not tell you the options available > that would work for you.
The limit is hardcode in application level and some which is in OS Level - tcp connection is no limit, but it may not be legal -
"Per development: The connection limit refers to the number of redirector-based connections and is enforced for any file, print, named pipe, or mail slot session. The TCP connection limit is not enforced, but it may be bound by legal agreement to not permit more than 10 clients. "
> > On Wed, 10 Dec 2003 10:01:44 -0800, "Vladimir Petter" > > <vlad...@hotmail.com> wrote:
> >>Dear All,
> >>May be somebody knows if there is a product that may be addressing following > >>issue:
> >> - On Windows 2000 Professional/XP Professional IIS (version 6.0) is > >>limited by 10 simultaneous TCP connections. > >>If 11'th connection comes it going to get HTTP error. > >> - IE uses HTTP 1.1 and Keep-Alive. If IE client made a connection to IIS > >>(and keep-alive is on) then IE will keep this connection > >>up to ~30 sec (even if does not have any requests to send). > >> - Each IE client makes up to 2 connections to the IIS and keeps them in > >>cash.
> >> So 10 simultaneous IE clients will eat up to 10 connections and 11'th > >>user may get an error. This becomes a limitation for my WEB application.
> >>What I am looking for is a Proxy that would not have limitation on number of > >>incoming TCP connections (IE to Proxy), but would be aware of IIS limitation > >>(10 connections on Professional platform) and put client's request on hold > >>until IIS connection would become available.
> > You won't find that, and it may not even be possible to write your > > own. The limit is inherent to the operating system, not IIS itself.
> That is false. The limit is coded into IIS. I have accepted more than 8000 > simultaneous TCP connections on Windows 2000 and XP Pro.
> >>I've already considered possibility of turning off keep-alive on the server > >>side and now interested only in discussion of the option described above > >>(Proxy).
> > Then I'll honor your request and not tell you the options available > > that would work for you.
Writing proxy wouldn't be a trivial task for low number of connections, if they were using HTTP1.0. However, both IIS and IE are using HTTP1.1 and persistent connections by default. And that's where things get much more complicated. Writing universal proxy for the purpose simply isn't worth the trouble.
Why don't you just buy Windows 2003 Server Web Edition? I would suspect that it would be cheaper than spending time/dev resources trying to write such a specialised proxy application that you are considering.
Cheers Ken
"Vladimir Petter" <vlad...@hotmail.com> wrote in message
news:uTbTPg0vDHA.684@TK2MSFTNGP09.phx.gbl... : Dear All, : : May be somebody knows if there is a product that may be addressing following : issue: : : - On Windows 2000 Professional/XP Professional IIS (version 6.0) is : limited by 10 simultaneous TCP connections. : If 11'th connection comes it going to get HTTP error. : - IE uses HTTP 1.1 and Keep-Alive. If IE client made a connection to IIS : (and keep-alive is on) then IE will keep this connection : up to ~30 sec (even if does not have any requests to send). : - Each IE client makes up to 2 connections to the IIS and keeps them in : cash. : : So 10 simultaneous IE clients will eat up to 10 connections and 11'th : user may get an error. This becomes a limitation for my WEB application. : : What I am looking for is a Proxy that would not have limitation on number of : incoming TCP connections (IE to Proxy), but would be aware of IIS limitation : (10 connections on Professional platform) and put client's request on hold : until IIS connection would become available. : : I've already considered possibility of turning off keep-alive on the server : side and now interested only in discussion of the option described above : (Proxy). : : Regards, : Vladimir. : : :
> The specific of my application is that it is not actually a public WEB site. > It is an internal company's site that may have about 10-15 clients. Because > of WinINet limitations (we are using WinInet on client extensively) we > increased max number of HTTP requests to 4 so now even 2 clients eating up 8 > IIS connections.
> Well I think I will try to write a kind of proxy I've described.
> > >Thanks for your answer. > > >I know that. I am looking for possibility to "work-around" this > limitation > > >without making customer upgrade to Server. > > >Any suggestions?
> > >Vladimir.
> > Vladimir,
> > The best you can hope for is to do this :
> > "If you use IIS 5.0 on Windows 2000 Professional or IIS 5.1 on > > Microsoft Windows XP Professional, disable HTTP keep-alives in the > > properties of the Web site. When you do this, a limit of 10 concurrent > > connections still exists, but IIS does not maintain connections for > > inactive users."
> > but you cannot get away from the 10 concurrent connection limit - its > > hard-coded in the 'desktop' versions of Windows 2000 and XP
>> "If you use IIS 5.0 on Windows 2000 Professional or IIS 5.1 on >> Microsoft Windows XP Professional, disable HTTP keep-alives in the >> properties of the Web site. When you do this, a limit of 10 concurrent >> connections still exists, but IIS does not maintain connections for >> inactive users."
>> but you cannot get away from the 10 concurrent connection limit - its >> hard-coded in the 'desktop' versions of Windows 2000 and XP
>Just to clarify this statement... The 10 concurrent connection limit is 'hard >coded' into IIS, not into XP. Even Windows 95 can have over 200 active TCP >connections with other server software.
To clarify a bit further...
The 10 connection limit *is* the result of the operating system and not IIS. The fact that other web server software, such as Apache, doesn't use the operating system as tightly doesn't change that fact. You only get ten network connections with a workstation OS.
>> You won't find that, and it may not even be possible to write your >> own. The limit is inherent to the operating system, not IIS itself.
>That is false. The limit is coded into IIS. I have accepted more than 8000 >simultaneous TCP connections on Windows 2000 and XP Pro.
TCP/IP connections, sure. But you're not dealing with strictly a TCP/IP connection when using IIS on a workstation operating system. TCP/IP connections aren't limited the same way file, print, pipes, etc. are limited. Unfortunately, IIS uses the Windows OS to handle the connection limits. You'll find that some other products, such as Apache, do not.
>From my current study it seams to me that proxy solution should work. The >limit of connections on Professional OS has nothing to do with IIS limit (10 >connections). So proxy should be able handle high number of incoming >connections and make sure that it does not go above 10 on IIS.
So since it's simple, write one. :)
Seriously, you said you only had 15 systems or something connecting, so the number of requests likely isn't terribly high. A caching proxy might get you part way, and writing a proxy (well, it's not really a proxy...) that simply submitted requests until the request got fulfilled might work. You may need to do some client-side work to enable it, but as long as your time has no value you'll save the expense of a server license.
>Well if there is other possibilities (except upgrade to Server) that I >overlooked then I really would like to hear it out :-).
How about Apache? It doesn't use the OS in the same integrated manner, and has no trouble with more than ten connections. You've already investigated the keep-alive issues, which is the only simple alternative.
The problem isn't your concept, the problem is you're unwilling to work within the limitations of a given product on a given operating system. I'd like a car that runs on tap water, gets 1,000 miles to the gallon and does 0-60 in 1.2 seconds, but unless I'm willing to design and build it myself I'm pretty unlikely to get it.
You know, if you converted to Linux, Apache and PHP, all things would be free and there would be world peace within the decade...
>"Jeff Cochran" <jcochran.nos...@naplesgov.com> wrote in message >news:3fdd8ffa.25427963@msnews.microsoft.com... >> On Wed, 10 Dec 2003 10:01:44 -0800, "Vladimir Petter" >> <vlad...@hotmail.com> wrote:
>> >Dear All,
>> >May be somebody knows if there is a product that may be addressing >following >> >issue:
>> > - On Windows 2000 Professional/XP Professional IIS (version 6.0) is >> >limited by 10 simultaneous TCP connections. >> >If 11'th connection comes it going to get HTTP error. >> > - IE uses HTTP 1.1 and Keep-Alive. If IE client made a connection to >IIS >> >(and keep-alive is on) then IE will keep this connection >> >up to ~30 sec (even if does not have any requests to send). >> > - Each IE client makes up to 2 connections to the IIS and keeps them >in >> >cash.
>> > So 10 simultaneous IE clients will eat up to 10 connections and 11'th >> >user may get an error. This becomes a limitation for my WEB application.
>> >What I am looking for is a Proxy that would not have limitation on number >of >> >incoming TCP connections (IE to Proxy), but would be aware of IIS >limitation >> >(10 connections on Professional platform) and put client's request on >hold >> >until IIS connection would become available.
>> You won't find that, and it may not even be possible to write your >> own. The limit is inherent to the operating system, not IIS itself.
>> >I've already considered possibility of turning off keep-alive on the >server >> >side and now interested only in discussion of the option described above >> >(Proxy).
>> Then I'll honor your request and not tell you the options available >> that would work for you.
Jeff Cochran wrote: >>>You won't find that, and it may not even be possible to write your >>>own. The limit is inherent to the operating system, not IIS itself.
>>That is false. The limit is coded into IIS. I have accepted more than 8000 >>simultaneous TCP connections on Windows 2000 and XP Pro.
> TCP/IP connections, sure. But you're not dealing with strictly a > TCP/IP connection when using IIS on a workstation operating system. > TCP/IP connections aren't limited the same way file, print, pipes, > etc. are limited. Unfortunately, IIS uses the Windows OS to handle > the connection limits. You'll find that some other products, such as > Apache, do not.
Sigh! You still do not understand... This has been hashed out MANY times here and on the IIS group. Even Microsoft says the 10 connection limit is coded into IIS, not the OS. To be specific, when IIS starts up, it determines if it is running on a desktop or server OS, and sets functional limits accordingly.
But let me clarify even more: I am referring to anonymous connections, NOT Windows authenticated connections. Even Apache will have a 10 user limit if using Windows authentication since that is controlled by the OS. However, non-authenticated connections are simply normal TCP connections and hence there is no limit.
Let me also be clear that I would never tell anyone that it is proper to use a desktop Windows OS as a web server for other than a test or personal site. I agree that the original poster should simply invest in a copy of 2000 or 2003 Server.
|
