tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Einfeldt" <ralph.einfe...@uptime-isc.de>
Subject RE: Quick help with Bindings
Date Fri, 24 Jan 2003 15:14:48 GMT
There was a post about this toppic some month ago.

As I couldn't find it in the public archives I resend it:

> -----Original Message-----
> From: W. Egan [mailto:khayman1122@hotmail.com]
> Sent: Sunday, October 27, 2002 6:14 PM
> To: Tomcat Users List; Nathan Phelps
> Subject: Re: Tomcat 4.1.12 taking IPs or Ports not assigned to it?
> 
> 
> Its a Microsoft design problem.  I guess.  If IIS listens on 
> port 80 on ANY address on a given machine, it binds 0.0.0.0:80. 
> It's called socket pooling. Nothing else will be able to bind 
> 80 once IIS is started.  And if something else starts first 
> and binds 80, IIS wont be able to. I ran into
> the same problem.  See this remedy:
> 
> "Socket Pooling (Binding IIS to 0.0.0.0:80)
> Socket pooling causes Internet Information Services (IIS) 5.0 
> to listen to all IP addresses, which can present a possible 
> security risk for secure domains with multiple networks. 
> Also, bandwidth throttling and performance adjustments will 
> apply to all Web sites configured for the same port (for
> example port 80). If bandwidth throttling or performance 
> tuning is being done on a per-site basis, socket pooling 
> will need to be disabled.
> To disable socket pooling, perform the following steps:
> cscript adsutil.vbs set w3svc/disablesocketpooling true
> The command replies as follows:
> disablesocketpooling : (BOOLEAN) True
> Stop and start the IISAdmin service.
> Restart the WWW service."
> 
> Once you do this, you can have both IIS and Apache/Tomcat 
> listening on port
> 80 on different IPs on the same machine.  No need for 
> multiple nic's and
> multiple network segments either.

> -----Original Message-----
> From: Dave Morrow [mailto:David.Morrow@autodata.net]
> Sent: Friday, January 24, 2003 3:24 PM
> To: 'tomcat-user@jakarta.apache.org'
> Subject: Quick help with Bindings
> 
> 
> Hi,
> 
> Unfortunately, this does not seem to isolate Tomcat to a single NIC/IP
> address and I cannot for the life of me figure out why?  
> Other servers on
> the same physical box (running IIS) will not start because 
> tomcat binds to
> port 80 on all IP's
> 
> Anyone with expertise in this ?  I would really appreciate some help.
> 

--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@jakarta.apache.org>


Mime
View raw message