I think that depends on how you set up the listen, doesn't it? if you have application A listen on ALL interfaces on port 80, then application B that starts up later will be blocked. However, if application A starts up and listens on 10.10.10.10:80, then B can listen on 10.10.10.11:80. in the latter case, a netstat -a|grep LISTEN (on unix) will show 10.10.10.10:80, not *:80, which it would in the former case. Am I correct?
-----Original Message----- From: Ralph Einfeldt [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 9:47 AM To: Tomcat Users List Subject: AW: Problems using same port for several services (even with different IP / hostname) You are wrong!!! Of course one can have serveral services listening on port 80 on one machine if each service used a unique virtual interface (IP). That's true for unix, linux and windows . > -----Urspr�ngliche Nachricht----- > Von: Tom Drake [mailto:[EMAIL PROTECTED]] > Gesendet: Donnerstag, 10. Januar 2002 16:40 > An: Tomcat Users List > Betreff: Re: Problems using same port for several services (even with > different IP / hostname) <snip/> > Contrary to your statement below, only one process may bind to the > same port (80 in this case) at the same time. <snip/> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
