tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Morrow <>
Subject RE: Quick help with Bindings
Date Fri, 24 Jan 2003 15:24:37 GMT
Wow.  It appears that MS is crazy enough to do such a thing after all!  I
don't believe it!

I thank you.  This solution solved the problem!

David Morrow
Network Administrator
Autodata Solutions Company
Ph: (519) 951-6067 Fax: (519) 451-6615

This message has originated from Autodata Solutions.  The attached material
is the Confidential and Proprietary Information of Autodata Solutions. This
email and any files transmitted with it are confidential and intended solely
for the use of the individual or entity to whom they are addressed. If you
have received this email in error please delete this message and notify the
Autodata system administrator at

-----Original Message-----
From: Ralph Einfeldt [] 
Sent: January 24, 2003 10:15 AM
To: Tomcat Users List
Subject: RE: Quick help with Bindings

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 []
> 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 
> 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
> 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 []
> Sent: Friday, January 24, 2003 3:24 PM
> To: ''
> 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:
For additional commands, e-mail:

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message