Re: TCP6

10.160.180.99:56843 10.160.180.99:4002 TIME_WAIT - tcp0 0 10.160.180.99:56842 10.160.180.99:4002 TIME_WAIT - tcp0 0 10.160.180.99:56889 10.160.180.99:4000 TIME_WAIT - tcp6 0 0 :::111 :::* LISTEN 413/rpcbind tcp6 0

Re: TCP6

0.160.180.99:35993 10.160.180.99:4001 >> TIME_WAIT - >> tcp0 0 10.160.180.99:56843 10.160.180.99:4002 >> TIME_WAIT - >> tcp0 0 10.160.180.99:56842 10.160.180.99:4002 >> TIME_WAIT - >> tcp0 0 10.160.180.99:56

Re: TCP6

0 10.160.180.99:56843 10.160.180.99:4002 TIME_WAIT - tcp0 0 10.160.180.99:56842 10.160.180.99:4002 TIME_WAIT - tcp0 0 10.160.180.99:56889 10.160.180.99:4000 TIME_WAIT - tcp6 0 0 :::111 :::* LISTEN 413/rpcbind tcp6

Re: TCP6

0 0 10.160.180.99:56843 10.160.180.99:4002 TIME_WAIT - tcp0 0 10.160.180.99:56842 10.160.180.99:4002 TIME_WAIT - tcp0 0 10.160.180.99:56889 10.160.180.99:4000 TIME_WAIT - tcp6 0 0 :::111 :::* LISTEN 413/rpcbind tcp6

Re: TCP6

tp* > > 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 > &

Re: TCP6

stances 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.9

Re: TCP6

; following netstat output: >> how I force the tomcat to bind to tcp instead of tcp6 >> > > Hi. As far as I know, this is more of a "java thing" than a "tomcat > thing". > (per "java" I mean the JVM that runs tomcat). > Search Goo

Re: TCP6

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 :::* >

Re: TCP6

On Sun, Mar 18, 2018 at 2:04 PM, Loai Abdallatif 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 > &g

Re: TCP6

On 18.03.2018 14:04, Loai Abdallatif 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 Hi. As far as I know, this is more of a "

TCP6

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

Re: unwanted tcp6 protocol in tribes listener socket;

rvers) > > Proto Recv-Q Send-QLocal Address Foreign > > Address State > > tcp6 0 0 myComputerName:4000 > > [::]:*LISTEN > > netstat -atn | grep -P ":4000\W"

Re: unwanted tcp6 protocol in tribes listener socket;

On Mon, 2013-02-04 at 17:51 +1300, Vince Stewart wrote: > Hi Tim, > thanks so much for your reply > netstat -t -l yields that includes: > Active Internet connections (only servers) > Proto Recv-Q Send-QLocal Address Foreign > Address St

Re: unwanted tcp6 protocol in tribes listener socket;

Hi Tim, thanks so much for your reply netstat -t -l yields that includes: Active Internet connections (only servers) Proto Recv-Q Send-QLocal Address Foreign Address State tcp6 0 0 myComputerName:4000

Re: unwanted tcp6 protocol in tribes listener socket;

host" address. > When this has run, the address for the listener is "127.0.0.1" in other > words an IPv4 address. > However the SocksSocketImpl object representing the real socket continues > to display the* useV4* property as *false* > and my Ubuntu system displays th