-
-
2. Re: IIS and Jboss/Jetty
mjdinsmore May 23, 2003 5:44 PM (in response to hank_mclaurin)On the surface, no there isn't any problems running both on the same server. We do that ourselves (as we port away from using IIS altogether).
One thing to be careful about --- IIS binds all the addresses by default. IIS 5.0 has a new feature named socket pooling which it uses on machines which have multiple IP addresses. Basically, when socket pooling is turned on, IIS will grab every IP address on the machine, even if it is explicitly configured to not use one or more of those addresses. The reason that it does so is explained in a KB about IIS -- http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q238/1/31.ASP&NoWebContent=1
Of course, this is if you run IIS on one IP and Jetty on the other (when they both use port 80). -
3. Re: IIS and Jboss/Jetty
mjdinsmore May 23, 2003 5:45 PM (in response to hank_mclaurin)On the surface, no there isn't any problems running both on the same server. We do that ourselves (as we port away from using IIS altogether).
One thing to be careful about --- IIS binds all the addresses by default. IIS 5.0 has a new feature named socket pooling which it uses on machines which have multiple IP addresses. Basically, when socket pooling is turned on, IIS will grab every IP address on the machine, even if it is explicitly configured to not use one or more of those addresses. The reason that it does so is explained in a KB about IIS -- http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q238/1/31.ASP&NoWebContent=1
Of course, this is if you run IIS on one IP and Jetty on the other (when they both use port 80).