On Sun, Mar 18, 2018 at 2:04 PM, Loai Abdallatif <loai.abdalla...@gmail.com> wrote:
> Dear Friends > > *root@appserver01:~# netstat -antp* > I have started three tomcat instances on one debian server and I got the > following netstat output: > how I force the tomcat to bind to tcp instead of tcp6 > > > tcp6 0 0 10.160.180.99:8005 :::* > LISTEN 742/java > tcp6 0 0 10.160.180.99:8105 :::* > LISTEN 804/java > tcp6 0 0 10.160.180.99:8009 :::* > LISTEN 742/java > tcp6 0 0 10.160.180.99:8109 :::* > LISTEN 804/java > tcp6 0 0 :::111 :::* > LISTEN 416/rpcbind > tcp6 0 0 10.160.180.99:8080 :::* > LISTEN 742/java > tcp6 0 0 10.160.180.99:8081 :::* > LISTEN 804/java > tcp6 0 0 :::22 :::* > LISTEN 496/sshd > tcp6 0 0 ::1:25 :::* > LISTEN 709/exim4 > tcp6 0 0 :::39098 :::* > LISTEN 425/rpc.statd > tcp6 0 0 10.160.180.99:4000 :::* > LISTEN 742/java > tcp6 0 0 10.160.180.99:4001 :::* > LISTEN 804/java > Loai, You did bind to IPv4 addresses, e.g. 10.160.180.99 8005 - shutdown port 8105 - probably shutdown port for your second Tomcat instance 8009 - probably your AJP port 8109 - probably your AJP port for your second Tomcat instance 8080 - http port 8081 - http port for your second Tomcat instance Cheers! Neven
