You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Loai Abdallatif <lo...@gmail.com> on 2018/03/18 13:04:17 UTC
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 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
Re: TCP6
Posted by Loai Abdallatif <lo...@gmail.com>.
yes
On Sun, Mar 18, 2018 at 3:56 PM, Neven Cvetkovic <ne...@gmail.com>
wrote:
> On Sun, Mar 18, 2018 at 2:04 PM, Loai Abdallatif <
> loai.abdallatif@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
>
Re: TCP6
Posted by Neven Cvetkovic <ne...@gmail.com>.
On Sun, Mar 18, 2018 at 2:04 PM, Loai Abdallatif <lo...@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
Re: TCP6
Posted by Loai Abdallatif <lo...@gmail.com>.
I will thanks
On Sun, Mar 18, 2018 at 3:56 PM, M. Manna <ma...@gmail.com> wrote:
> In your server.xml add address="0.0.0.0" for connector.
>
> On 18 Mar 2018 1:04 pm, "Loai Abdallatif" <lo...@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
> >
>
Re: TCP6
Posted by "André Warnier (tomcat)" <aw...@ice-sa.com>.
On 18.03.2018 15:17, Loai Abdallatif wrote:
> Yes sure, I have added the below lines to /etc/sysctl.conf
>
> net.ipv6.conf.all.disable_ipv6 = 1net.ipv6.conf.default.disable_ipv6 =
> 1net.ipv6.conf.lo.disable_ipv6 = 1net.ipv6.conf.eth0.disable_ipv6 = 1
>
Is that not a bit excessive ? you have totally disabled IPv6 for the whole system.
So nobody who is using IPv6 will be able to communicate with your system, and none of the
programs running on your system will be able to communicate with any other host using IPv6.
>
>
> On Sun, Mar 18, 2018 at 4:14 PM, André Warnier (tomcat) <aw...@ice-sa.com>
> wrote:
>
>> On 18.03.2018 15:06, Loai Abdallatif wrote:
>>
>>> Hello All
>>>
>>> I disabled ip6
>>>
>>
>> thanks for saying that, but you do not say how you did that.
>> Please say, so that future readers of the tomcat users mailing lists
>> archives
>> (http://tomcat.apache.org/lists.html#Apache_Tomcat_Mailing_Lists)
>> will find it, and not need to ask again.
>>
>> and restarted the machine , and its working now\
>>
>>> root@appserver01:/opt/tomcat/controller# netstat -antp
>>> Active Internet connections (servers and established)
>>> Proto Recv-Q Send-Q Local Address Foreign Address
>>> State PID/Program name
>>> tcp 0 0 10.160.180.99:4002 0.0.0.0:*
>>> LISTEN 871/java
>>> tcp 0 0 10.160.180.99:8005 0.0.0.0:*
>>> LISTEN 730/java
>>> tcp 0 0 0.0.0.0:46022 0.0.0.0:*
>>> LISTEN 422/rpc.statd
>>> tcp 0 0 10.160.180.99:8105 0.0.0.0:*
>>> LISTEN 799/java
>>> tcp 0 0 10.160.180.99:8009 0.0.0.0:*
>>> LISTEN 730/java
>>> tcp 0 0 10.160.180.99:8109 0.0.0.0:*
>>> LISTEN 799/java
>>> tcp 0 0 0.0.0.0:111 0.0.0.0:*
>>> LISTEN 413/rpcbind
>>> tcp 0 0 10.160.180.99:8080 0.0.0.0:*
>>> LISTEN 730/java
>>> tcp 0 0 10.160.180.99:8209 0.0.0.0:*
>>> LISTEN 871/java
>>> tcp 0 0 10.160.180.99:8081 0.0.0.0:*
>>> LISTEN 799/java
>>> tcp 0 0 10.160.180.99:8082 0.0.0.0:*
>>> LISTEN 871/java
>>> tcp 0 0 0.0.0.0:22 0.0.0.0:*
>>> LISTEN 457/sshd
>>> tcp 0 0 10.160.180.99:4000 0.0.0.0:*
>>> LISTEN 730/java
>>> tcp 0 0 10.160.180.99:4001 0.0.0.0:*
>>> LISTEN 799/java
>>> tcp 0 464 10.160.180.99:22 10.160.1.14:54236
>>> ESTABLISHED 710/0
>>> tcp 0 0 10.160.180.99:35993 10.160.180.99:4001
>>> TIME_WAIT -
>>> tcp 0 0 10.160.180.99:56843 10.160.180.99:4002
>>> TIME_WAIT -
>>> tcp 0 0 10.160.180.99:56842 10.160.180.99:4002
>>> TIME_WAIT -
>>> tcp 0 0 10.160.180.99:56889 10.160.180.99:4000
>>> TIME_WAIT -
>>> tcp6 0 0 :::111 :::*
>>> LISTEN 413/rpcbind
>>> tcp6 0 0 :::22 :::*
>>> LISTEN 457/sshd
>>> tcp6 0 0 :::50203 :::*
>>> LISTEN 422/rpc.statd
>>>
>>>
>>> On Sun, Mar 18, 2018 at 3:56 PM, M. Manna <ma...@gmail.com> wrote:
>>>
>>> In your server.xml add address="0.0.0.0" for connector.
>>>>
>>>> On 18 Mar 2018 1:04 pm, "Loai Abdallatif" <lo...@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
>>>>>
>>>>>
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: TCP6
Posted by Loai Abdallatif <lo...@gmail.com>.
Yes sure, I have added the below lines to /etc/sysctl.conf
net.ipv6.conf.all.disable_ipv6 = 1net.ipv6.conf.default.disable_ipv6 =
1net.ipv6.conf.lo.disable_ipv6 = 1net.ipv6.conf.eth0.disable_ipv6 = 1
On Sun, Mar 18, 2018 at 4:14 PM, André Warnier (tomcat) <aw...@ice-sa.com>
wrote:
> On 18.03.2018 15:06, Loai Abdallatif wrote:
>
>> Hello All
>>
>> I disabled ip6
>>
>
> thanks for saying that, but you do not say how you did that.
> Please say, so that future readers of the tomcat users mailing lists
> archives
> (http://tomcat.apache.org/lists.html#Apache_Tomcat_Mailing_Lists)
> will find it, and not need to ask again.
>
> and restarted the machine , and its working now\
>
>> root@appserver01:/opt/tomcat/controller# netstat -antp
>> Active Internet connections (servers and established)
>> Proto Recv-Q Send-Q Local Address Foreign Address
>> State PID/Program name
>> tcp 0 0 10.160.180.99:4002 0.0.0.0:*
>> LISTEN 871/java
>> tcp 0 0 10.160.180.99:8005 0.0.0.0:*
>> LISTEN 730/java
>> tcp 0 0 0.0.0.0:46022 0.0.0.0:*
>> LISTEN 422/rpc.statd
>> tcp 0 0 10.160.180.99:8105 0.0.0.0:*
>> LISTEN 799/java
>> tcp 0 0 10.160.180.99:8009 0.0.0.0:*
>> LISTEN 730/java
>> tcp 0 0 10.160.180.99:8109 0.0.0.0:*
>> LISTEN 799/java
>> tcp 0 0 0.0.0.0:111 0.0.0.0:*
>> LISTEN 413/rpcbind
>> tcp 0 0 10.160.180.99:8080 0.0.0.0:*
>> LISTEN 730/java
>> tcp 0 0 10.160.180.99:8209 0.0.0.0:*
>> LISTEN 871/java
>> tcp 0 0 10.160.180.99:8081 0.0.0.0:*
>> LISTEN 799/java
>> tcp 0 0 10.160.180.99:8082 0.0.0.0:*
>> LISTEN 871/java
>> tcp 0 0 0.0.0.0:22 0.0.0.0:*
>> LISTEN 457/sshd
>> tcp 0 0 10.160.180.99:4000 0.0.0.0:*
>> LISTEN 730/java
>> tcp 0 0 10.160.180.99:4001 0.0.0.0:*
>> LISTEN 799/java
>> tcp 0 464 10.160.180.99:22 10.160.1.14:54236
>> ESTABLISHED 710/0
>> tcp 0 0 10.160.180.99:35993 10.160.180.99:4001
>> TIME_WAIT -
>> tcp 0 0 10.160.180.99:56843 10.160.180.99:4002
>> TIME_WAIT -
>> tcp 0 0 10.160.180.99:56842 10.160.180.99:4002
>> TIME_WAIT -
>> tcp 0 0 10.160.180.99:56889 10.160.180.99:4000
>> TIME_WAIT -
>> tcp6 0 0 :::111 :::*
>> LISTEN 413/rpcbind
>> tcp6 0 0 :::22 :::*
>> LISTEN 457/sshd
>> tcp6 0 0 :::50203 :::*
>> LISTEN 422/rpc.statd
>>
>>
>> On Sun, Mar 18, 2018 at 3:56 PM, M. Manna <ma...@gmail.com> wrote:
>>
>> In your server.xml add address="0.0.0.0" for connector.
>>>
>>> On 18 Mar 2018 1:04 pm, "Loai Abdallatif" <lo...@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
>>>>
>>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: TCP6
Posted by "André Warnier (tomcat)" <aw...@ice-sa.com>.
On 18.03.2018 15:06, Loai Abdallatif wrote:
> Hello All
>
> I disabled ip6
thanks for saying that, but you do not say how you did that.
Please say, so that future readers of the tomcat users mailing lists archives
(http://tomcat.apache.org/lists.html#Apache_Tomcat_Mailing_Lists)
will find it, and not need to ask again.
and restarted the machine , and its working now\
> root@appserver01:/opt/tomcat/controller# netstat -antp
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address Foreign Address
> State PID/Program name
> tcp 0 0 10.160.180.99:4002 0.0.0.0:*
> LISTEN 871/java
> tcp 0 0 10.160.180.99:8005 0.0.0.0:*
> LISTEN 730/java
> tcp 0 0 0.0.0.0:46022 0.0.0.0:*
> LISTEN 422/rpc.statd
> tcp 0 0 10.160.180.99:8105 0.0.0.0:*
> LISTEN 799/java
> tcp 0 0 10.160.180.99:8009 0.0.0.0:*
> LISTEN 730/java
> tcp 0 0 10.160.180.99:8109 0.0.0.0:*
> LISTEN 799/java
> tcp 0 0 0.0.0.0:111 0.0.0.0:*
> LISTEN 413/rpcbind
> tcp 0 0 10.160.180.99:8080 0.0.0.0:*
> LISTEN 730/java
> tcp 0 0 10.160.180.99:8209 0.0.0.0:*
> LISTEN 871/java
> tcp 0 0 10.160.180.99:8081 0.0.0.0:*
> LISTEN 799/java
> tcp 0 0 10.160.180.99:8082 0.0.0.0:*
> LISTEN 871/java
> tcp 0 0 0.0.0.0:22 0.0.0.0:*
> LISTEN 457/sshd
> tcp 0 0 10.160.180.99:4000 0.0.0.0:*
> LISTEN 730/java
> tcp 0 0 10.160.180.99:4001 0.0.0.0:*
> LISTEN 799/java
> tcp 0 464 10.160.180.99:22 10.160.1.14:54236
> ESTABLISHED 710/0
> tcp 0 0 10.160.180.99:35993 10.160.180.99:4001
> TIME_WAIT -
> tcp 0 0 10.160.180.99:56843 10.160.180.99:4002
> TIME_WAIT -
> tcp 0 0 10.160.180.99:56842 10.160.180.99:4002
> TIME_WAIT -
> tcp 0 0 10.160.180.99:56889 10.160.180.99:4000
> TIME_WAIT -
> tcp6 0 0 :::111 :::*
> LISTEN 413/rpcbind
> tcp6 0 0 :::22 :::*
> LISTEN 457/sshd
> tcp6 0 0 :::50203 :::*
> LISTEN 422/rpc.statd
>
>
> On Sun, Mar 18, 2018 at 3:56 PM, M. Manna <ma...@gmail.com> wrote:
>
>> In your server.xml add address="0.0.0.0" for connector.
>>
>> On 18 Mar 2018 1:04 pm, "Loai Abdallatif" <lo...@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
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: TCP6
Posted by Loai Abdallatif <lo...@gmail.com>.
Hello All
I disabled ip6 and restarted the machine , and its working now\
root@appserver01:/opt/tomcat/controller# netstat -antp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address
State PID/Program name
tcp 0 0 10.160.180.99:4002 0.0.0.0:*
LISTEN 871/java
tcp 0 0 10.160.180.99:8005 0.0.0.0:*
LISTEN 730/java
tcp 0 0 0.0.0.0:46022 0.0.0.0:*
LISTEN 422/rpc.statd
tcp 0 0 10.160.180.99:8105 0.0.0.0:*
LISTEN 799/java
tcp 0 0 10.160.180.99:8009 0.0.0.0:*
LISTEN 730/java
tcp 0 0 10.160.180.99:8109 0.0.0.0:*
LISTEN 799/java
tcp 0 0 0.0.0.0:111 0.0.0.0:*
LISTEN 413/rpcbind
tcp 0 0 10.160.180.99:8080 0.0.0.0:*
LISTEN 730/java
tcp 0 0 10.160.180.99:8209 0.0.0.0:*
LISTEN 871/java
tcp 0 0 10.160.180.99:8081 0.0.0.0:*
LISTEN 799/java
tcp 0 0 10.160.180.99:8082 0.0.0.0:*
LISTEN 871/java
tcp 0 0 0.0.0.0:22 0.0.0.0:*
LISTEN 457/sshd
tcp 0 0 10.160.180.99:4000 0.0.0.0:*
LISTEN 730/java
tcp 0 0 10.160.180.99:4001 0.0.0.0:*
LISTEN 799/java
tcp 0 464 10.160.180.99:22 10.160.1.14:54236
ESTABLISHED 710/0
tcp 0 0 10.160.180.99:35993 10.160.180.99:4001
TIME_WAIT -
tcp 0 0 10.160.180.99:56843 10.160.180.99:4002
TIME_WAIT -
tcp 0 0 10.160.180.99:56842 10.160.180.99:4002
TIME_WAIT -
tcp 0 0 10.160.180.99:56889 10.160.180.99:4000
TIME_WAIT -
tcp6 0 0 :::111 :::*
LISTEN 413/rpcbind
tcp6 0 0 :::22 :::*
LISTEN 457/sshd
tcp6 0 0 :::50203 :::*
LISTEN 422/rpc.statd
On Sun, Mar 18, 2018 at 3:56 PM, M. Manna <ma...@gmail.com> wrote:
> In your server.xml add address="0.0.0.0" for connector.
>
> On 18 Mar 2018 1:04 pm, "Loai Abdallatif" <lo...@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
> >
>
Re: TCP6
Posted by "M. Manna" <ma...@gmail.com>.
In your server.xml add address="0.0.0.0" for connector.
On 18 Mar 2018 1:04 pm, "Loai Abdallatif" <lo...@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
>
Re: TCP6
Posted by Loai Abdallatif <lo...@gmail.com>.
Thanks
On Sun, Mar 18, 2018 at 3:57 PM, André Warnier (tomcat) <aw...@ice-sa.com>
wrote:
> 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 "java thing" than a "tomcat
> thing".
> (per "java" I mean the JVM that runs tomcat).
> Search Google for "java prefer ipv4" for some answers.
>
>
>>
>> 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
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: TCP6
Posted by "André Warnier (tomcat)" <aw...@ice-sa.com>.
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 "java thing" than a "tomcat thing".
(per "java" I mean the JVM that runs tomcat).
Search Google for "java prefer ipv4" for some answers.
>
>
> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org