You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by "Peter J. Cranstone" <cr...@msn.com> on 2003/11/18 21:00:34 UTC

Apache + Windows

Bill,

Here is an interesting link to a problem someone encountered running Apache
on Windows. If he's right there is little hope for Apache to ever run
properly on newer versions of Windows.

http://grumet.net/weblog/archives/2003/11/18/questions_about_windows_apache.
html

Regards,



Peter

Re: Apache + Windows

Posted by "William A. Rowe, Jr." <wr...@apache.org>.
At 02:34 PM 11/18/2003, Bill Stoddard wrote:
>Peter J. Cranstone wrote:
>
>If I am not mistaken, I seem to recall that TransmitFile() is artifically limited to serving no more than 10 TCP connections on non server editions of Windows. I've not actually tried it myself.

Not TCP connections.

This limit comes into play through the authentication manager.  There
is a hardcoded limit of the number of users who can be simultaniously
authenticated through the winnt login manager.

mod_auth_ntlm/mod_auth_sspi etc can all be victims of this limit.

Bill 


Re: Apache + Windows

Posted by Ian Holsman <li...@holsman.net>.
Jess Holle wrote:
> In other words, you can choose free, open-source software applications 
> [client or server], but if you want a Microsoft server then you still 
> have to pay for a Microsoft server OS.
> 
> This makes some sense -- all the more reason for the cost sensitive 
> (among others) to use something else.
> 
> -- 
> Jess Holle
>
[offtopic]
have you seen the price of the 'server' version of any of the major 
linux vendors?
I think MS Server may be cheaper if you want a supported corporate type 
machine


Re: Apache + Windows

Posted by Jess Holle <je...@ptc.com>.
In other words, you can choose free, open-source software applications 
[client or server], but if you want a Microsoft server then you still 
have to pay for a Microsoft server OS.

This makes some sense -- all the more reason for the cost sensitive 
(among others) to use something else.

--
Jess Holle

Andrew Mann wrote:

> http://www.microsoft.com/mspress/books/sampchap/5726.asp
>
> "Also, because TransmitFile is geared toward server applications, it 
> is fully functional only on server versions of Windows. On home and 
> professional versions, there may be only two outstanding TransmitFile 
> (or TransmitPackets) calls at any given time. If there are more, then 
> they are queued and not processed until the executing calls are 
> finished."
>
>     It's not as official as MSDN I guess, but at least it's published 
> by them.  The article appears to be XP era.
>
> Andrew
>
> Bill Stoddard wrote:
>
>> Peter J. Cranstone wrote:
>>
>>> Bill,
>>>
>>> Here is an interesting link to a problem someone encountered running 
>>> Apache
>>> on Windows. If he's right there is little hope for Apache to ever run
>>> properly on newer versions of Windows.
>>>
>>> http://grumet.net/weblog/archives/2003/11/18/questions_about_windows_apache. 
>>>
>>> html
>>>
>>> Regards,
>>>
>>>
>>>
>>> Peter
>>>
>>>
>>
>> If I am not mistaken, I seem to recall that TransmitFile() is 
>> artifically limited to serving no more than 10 TCP connections on non 
>> server editions of Windows. I've not actually tried it myself.
>>
>> Bill
>>
>
>



Re: Apache + Windows

Posted by Andrew Mann <am...@crosslink.net>.
Jeff White wrote:

>From: "Bill Stoddard"
>
>
>  
>
>>Andrew Mann wrote:
>>
>>    
>>
>>>http://www.microsoft.com/mspress/books/sampchap/5726.asp
>>>
>>>"Also, because TransmitFile is geared toward server applications,
>>>      
>>>
>it is
>  
>
>>>fully functional only on server versions of Windows. On home and
>>>professional versions, there may be only two outstanding
>>>      
>>>
>TransmitFile
>  
>
>>>(or TransmitPackets) calls at any given time. If there are more,
>>>      
>>>
>then
>  
>
>>>they are queued and not processed until the executing calls are
>>>      
>>>
>finished."
>  
>
>>>    It's not as official as MSDN I guess, but at least it's
>>>      
>>>
>published by
>  
>
>>>them.  The article appears to be XP era.
>>>
>>>Andrew
>>>      
>>>
>>Yep, checkout MaxActiveTransmitFileCount here:
>>
>>    
>>
>http://www.microsoft.com/technet/treeview/default.asp?url=/technet/itsolutions/network/deploy/depovg/tcpip2k.asp
>  
>
>>Can work around this particular fooness with EnableSendfile off. No
>>    
>>
>idea if this will make teh problem
>  
>
>>disappear tho.
>>
>>Bill
>>
>>    
>>
>
>Try using the built-in Windows Script Host (WSH)
>and the built-in (WMI) Windows Management
>Instrumentation via the built-in Windows Scripting
>language VBScript.
>
>Set the Allowed Number of TCP Connections
>http://www.microsoft.com/technet/scriptcenter/network/scnet133.asp
>
>Save the above little VBScript as whatever.vbs
>and start it by using the command line
>version of the Windows Script Host - cscript.exe.
>
>c:>cscript.exe whatever.vbs
>
>Try the other "networking options" too.
>
>Networking
>http://www.microsoft.com/technet/scriptcenter/network/default.asp
>
>And for doing registry actions.
>
>Registry
>http://www.microsoft.com/technet/scriptcenter/registry/default.asp
>
>All done via the built-in Windows Scripting
>engine and the built-in languages (or download
>and use the language of your desire with the
>built-in Windows Script Host engines).
>
>Administration scripting examples and an
>ONLINE version of the 1328 page Scripting Guide:
>http://www.microsoft.com/technet/scriptcenter
>
>Jeff
>
>
>  
>
    I don't think any of that applies to this situation.  The way I read 
the URL Bill provided is that MaxActiveTransmitFileCount is hard coded 
in workstation builds, no amount of registry editing can override it.
It doesn't seem to be an issue of exceeding the maximum number of TCP 
connections, but rather that TransmitFile() is used to send files when 
EnableSendfile is configured on in Apache, and that function is crippled 
in Windows Workstation builds.
As far as I can tell this is something directed solely at web servers 
(at least I can't think of much else that would need to serve massive 
amounts of small files uninterpretted over the network).

Andrew


Re: Apache + Windows

Posted by Jeff White <jl...@earthlink.net>.
From: "Bill Stoddard"


> Andrew Mann wrote:
>
> > http://www.microsoft.com/mspress/books/sampchap/5726.asp
> >
> > "Also, because TransmitFile is geared toward server applications,
it is
> > fully functional only on server versions of Windows. On home and
> > professional versions, there may be only two outstanding
TransmitFile
> > (or TransmitPackets) calls at any given time. If there are more,
then
> > they are queued and not processed until the executing calls are
finished."
> >
> >     It's not as official as MSDN I guess, but at least it's
published by
> > them.  The article appears to be XP era.
> >
> > Andrew
>
> Yep, checkout MaxActiveTransmitFileCount here:
>
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/itsolutions/network/deploy/depovg/tcpip2k.asp
>
> Can work around this particular fooness with EnableSendfile off. No
idea if this will make teh problem
> disappear tho.
>
> Bill
>

Try using the built-in Windows Script Host (WSH)
and the built-in (WMI) Windows Management
Instrumentation via the built-in Windows Scripting
language VBScript.

Set the Allowed Number of TCP Connections
http://www.microsoft.com/technet/scriptcenter/network/scnet133.asp

Save the above little VBScript as whatever.vbs
and start it by using the command line
version of the Windows Script Host - cscript.exe.

c:>cscript.exe whatever.vbs

Try the other "networking options" too.

Networking
http://www.microsoft.com/technet/scriptcenter/network/default.asp

And for doing registry actions.

Registry
http://www.microsoft.com/technet/scriptcenter/registry/default.asp

All done via the built-in Windows Scripting
engine and the built-in languages (or download
and use the language of your desire with the
built-in Windows Script Host engines).

Administration scripting examples and an
ONLINE version of the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scriptcenter

Jeff







Re: Apache + Windows

Posted by Bill Stoddard <bi...@wstoddard.com>.
Andrew Mann wrote:

> http://www.microsoft.com/mspress/books/sampchap/5726.asp
> 
> "Also, because TransmitFile is geared toward server applications, it is 
> fully functional only on server versions of Windows. On home and 
> professional versions, there may be only two outstanding TransmitFile 
> (or TransmitPackets) calls at any given time. If there are more, then 
> they are queued and not processed until the executing calls are finished."
> 
>     It's not as official as MSDN I guess, but at least it's published by 
> them.  The article appears to be XP era.
> 
> Andrew

Yep, checkout MaxActiveTransmitFileCount here:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/itsolutions/network/deploy/depovg/tcpip2k.asp

Can work around this particular fooness with EnableSendfile off. No idea if this will make teh problem 
disappear tho.

Bill


Re: Apache + Windows

Posted by Andrew Mann <am...@crosslink.net>.
http://www.microsoft.com/mspress/books/sampchap/5726.asp

"Also, because TransmitFile is geared toward server applications, it is 
fully functional only on server versions of Windows. On home and 
professional versions, there may be only two outstanding TransmitFile 
(or TransmitPackets) calls at any given time. If there are more, then 
they are queued and not processed until the executing calls are finished."

	It's not as official as MSDN I guess, but at least it's published by 
them.  The article appears to be XP era.

Andrew

Bill Stoddard wrote:
> Peter J. Cranstone wrote:
> 
>> Bill,
>>
>> Here is an interesting link to a problem someone encountered running 
>> Apache
>> on Windows. If he's right there is little hope for Apache to ever run
>> properly on newer versions of Windows.
>>
>> http://grumet.net/weblog/archives/2003/11/18/questions_about_windows_apache. 
>>
>> html
>>
>> Regards,
>>
>>
>>
>> Peter
>>
>>
> 
> If I am not mistaken, I seem to recall that TransmitFile() is 
> artifically limited to serving no more than 10 TCP connections on non 
> server editions of Windows. I've not actually tried it myself.
> 
> Bill
> 


Re: Apache + Windows

Posted by Jeff White <jl...@earthlink.net>.
From: "Bill Stoddard"


> Peter J. Cranstone wrote:
>
> > Bill,
> >
> > Here is an interesting link to a problem someone encountered
running Apache
> > on Windows. If he's right there is little hope for Apache to ever
run
> > properly on newer versions of Windows.
> >
> >
http://grumet.net/weblog/archives/2003/11/18/questions_about_windows_apache.
> > html
> >
> > Regards,
> >
> >
> >
> > Peter
> >
> >
>
> If I am not mistaken, I seem to recall that TransmitFile() is
artifically limited to serving no more than 10
> TCP connections on non server editions of Windows. I've not actually
tried it myself.
>
> Bill
>

Yes all "networking actions" are Workstation adjusted.

And only 5 for Windows XP Home Edition.

Microsoft Windows XP Professional
Resource Kit Documentation
Page 1539 last two paragraphs.

Or

Networking Features
http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/prhh_not_gehy.asp


Jeff






Re: Apache + Windows

Posted by Bill Stoddard <bi...@wstoddard.com>.
Peter J. Cranstone wrote:

> Bill,
> 
> Here is an interesting link to a problem someone encountered running Apache
> on Windows. If he's right there is little hope for Apache to ever run
> properly on newer versions of Windows.
> 
> http://grumet.net/weblog/archives/2003/11/18/questions_about_windows_apache.
> html
> 
> Regards,
> 
> 
> 
> Peter
> 
> 

If I am not mistaken, I seem to recall that TransmitFile() is artifically limited to serving no more than 10 
TCP connections on non server editions of Windows. I've not actually tried it myself.

Bill