date:20180318

Re: TCP6

2018-03-18 Thread tomcat


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) 
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
tcp0  0 10.160.180.99:4002  0.0.0.0:*
LISTEN  871/java
tcp0  0 10.160.180.99:8005  0.0.0.0:*
LISTEN  730/java
tcp0  0 0.0.0.0:46022   0.0.0.0:*
LISTEN  422/rpc.statd
tcp0  0 10.160.180.99:8105  0.0.0.0:*
LISTEN  799/java
tcp0  0 10.160.180.99:8009  0.0.0.0:*
LISTEN  730/java
tcp0  0 10.160.180.99:8109  0.0.0.0:*
LISTEN  799/java
tcp0  0 0.0.0.0:111 0.0.0.0:*
LISTEN  413/rpcbind
tcp0  0 10.160.180.99:8080  0.0.0.0:*
LISTEN  730/java
tcp0  0 10.160.180.99:8209  0.0.0.0:*
LISTEN  871/java
tcp0  0 10.160.180.99:8081  0.0.0.0:*
LISTEN  799/java
tcp0  0 10.160.180.99:8082  0.0.0.0:*
LISTEN  871/java
tcp0  0 0.0.0.0:22  0.0.0.0:*
LISTEN  457/sshd
tcp0  0 10.160.180.99:4000  0.0.0.0:*
LISTEN  730/java
tcp0  0 10.160.180.99:4001  0.0.0.0:*
LISTEN  799/java
tcp0464 10.160.180.99:2210.160.1.14:54236
ESTABLISHED 710/0
tcp0  0 10.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: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  wrote:

In your server.xml add address="0.0.0.0" for connector.


On 18 Mar 2018 1: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


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-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org







-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: TCP6

2018-03-18 Thread Loai Abdallatif

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) 
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
>> tcp0  0 10.160.180.99:4002  0.0.0.0:*
>> LISTEN  871/java
>> tcp0  0 10.160.180.99:8005  0.0.0.0:*
>> LISTEN  730/java
>> tcp0  0 0.0.0.0:46022   0.0.0.0:*
>> LISTEN  422/rpc.statd
>> tcp0  0 10.160.180.99:8105  0.0.0.0:*
>> LISTEN  799/java
>> tcp0  0 10.160.180.99:8009  0.0.0.0:*
>> LISTEN  730/java
>> tcp0  0 10.160.180.99:8109  0.0.0.0:*
>> LISTEN  799/java
>> tcp0  0 0.0.0.0:111 0.0.0.0:*
>> LISTEN  413/rpcbind
>> tcp0  0 10.160.180.99:8080  0.0.0.0:*
>> LISTEN  730/java
>> tcp0  0 10.160.180.99:8209  0.0.0.0:*
>> LISTEN  871/java
>> tcp0  0 10.160.180.99:8081  0.0.0.0:*
>> LISTEN  799/java
>> tcp0  0 10.160.180.99:8082  0.0.0.0:*
>> LISTEN  871/java
>> tcp0  0 0.0.0.0:22  0.0.0.0:*
>> LISTEN  457/sshd
>> tcp0  0 10.160.180.99:4000  0.0.0.0:*
>> LISTEN  730/java
>> tcp0  0 10.160.180.99:4001  0.0.0.0:*
>> LISTEN  799/java
>> tcp0464 10.160.180.99:2210.160.1.14:54236
>> ESTABLISHED 710/0
>> tcp0  0 10.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: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  wrote:
>>
>> In your server.xml add address="0.0.0.0" for connector.
>>>
>>> On 18 Mar 2018 1: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


 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-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: TCP6

2018-03-18 Thread tomcat


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
tcp0  0 10.160.180.99:4002  0.0.0.0:*
LISTEN  871/java
tcp0  0 10.160.180.99:8005  0.0.0.0:*
LISTEN  730/java
tcp0  0 0.0.0.0:46022   0.0.0.0:*
LISTEN  422/rpc.statd
tcp0  0 10.160.180.99:8105  0.0.0.0:*
LISTEN  799/java
tcp0  0 10.160.180.99:8009  0.0.0.0:*
LISTEN  730/java
tcp0  0 10.160.180.99:8109  0.0.0.0:*
LISTEN  799/java
tcp0  0 0.0.0.0:111 0.0.0.0:*
LISTEN  413/rpcbind
tcp0  0 10.160.180.99:8080  0.0.0.0:*
LISTEN  730/java
tcp0  0 10.160.180.99:8209  0.0.0.0:*
LISTEN  871/java
tcp0  0 10.160.180.99:8081  0.0.0.0:*
LISTEN  799/java
tcp0  0 10.160.180.99:8082  0.0.0.0:*
LISTEN  871/java
tcp0  0 0.0.0.0:22  0.0.0.0:*
LISTEN  457/sshd
tcp0  0 10.160.180.99:4000  0.0.0.0:*
LISTEN  730/java
tcp0  0 10.160.180.99:4001  0.0.0.0:*
LISTEN  799/java
tcp0464 10.160.180.99:2210.160.1.14:54236
ESTABLISHED 710/0
tcp0  0 10.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: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  wrote:


In your server.xml add address="0.0.0.0" for connector.

On 18 Mar 2018 1: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


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-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: TCP6

2018-03-18 Thread Loai Abdallatif

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
tcp0  0 10.160.180.99:4002  0.0.0.0:*
LISTEN  871/java
tcp0  0 10.160.180.99:8005  0.0.0.0:*
LISTEN  730/java
tcp0  0 0.0.0.0:46022   0.0.0.0:*
LISTEN  422/rpc.statd
tcp0  0 10.160.180.99:8105  0.0.0.0:*
LISTEN  799/java
tcp0  0 10.160.180.99:8009  0.0.0.0:*
LISTEN  730/java
tcp0  0 10.160.180.99:8109  0.0.0.0:*
LISTEN  799/java
tcp0  0 0.0.0.0:111 0.0.0.0:*
LISTEN  413/rpcbind
tcp0  0 10.160.180.99:8080  0.0.0.0:*
LISTEN  730/java
tcp0  0 10.160.180.99:8209  0.0.0.0:*
LISTEN  871/java
tcp0  0 10.160.180.99:8081  0.0.0.0:*
LISTEN  799/java
tcp0  0 10.160.180.99:8082  0.0.0.0:*
LISTEN  871/java
tcp0  0 0.0.0.0:22  0.0.0.0:*
LISTEN  457/sshd
tcp0  0 10.160.180.99:4000  0.0.0.0:*
LISTEN  730/java
tcp0  0 10.160.180.99:4001  0.0.0.0:*
LISTEN  799/java
tcp0464 10.160.180.99:2210.160.1.14:54236
ESTABLISHED 710/0
tcp0  0 10.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: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  wrote:

> In your server.xml add address="0.0.0.0" for connector.
>
> On 18 Mar 2018 1: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
> >
> >
> > 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

2018-03-18 Thread Loai Abdallatif

I will thanks

On Sun, Mar 18, 2018 at 3:56 PM, M. Manna  wrote:

> In your server.xml add address="0.0.0.0" for connector.
>
> On 18 Mar 2018 1: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
> >
> >
> > 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

2018-03-18 Thread Loai Abdallatif

yes

On Sun, Mar 18, 2018 at 3:56 PM, Neven Cvetkovic 
wrote:

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

Re: TCP6

2018-03-18 Thread Loai Abdallatif

Thanks

On Sun, Mar 18, 2018 at 3:57 PM, André Warnier (tomcat) 
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-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: TCP6

2018-03-18 Thread M. Manna

In your server.xml add address="0.0.0.0" for connector.

On 18 Mar 2018 1: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
>
>
> 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

2018-03-18 Thread Neven Cvetkovic

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

2018-03-18 Thread tomcat


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-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

TCP6

2018-03-18 Thread Loai Abdallatif

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: I cant start Tomcat instances

2018-03-18 Thread Loai Abdallatif

Thanks Olaf very much , I will review he steps

On Sun, Mar 18, 2018 at 12:13 PM, Olaf Kock  wrote:

>
>
> On 17.03.2018 19:16, Loai Abdallatif wrote:
>
>> actually all of them has X permissions
>>
>> -rwxr--r-- 1 root   root  70 Mar 17 11:59 shutdown-instance0.sh
>> -rwxr--r-- 1 root   root  70 Mar 17 11:48 shutdown-instance1.sh
>> -rwxr--r-- 1 root   root  70 Mar 17 11:59 shutdown-instance2.sh
>> -rwxr--r-- 1 root   root  69 Mar 17 11:58 startup-instance0.sh
>> -rwxr--r-- 1 tomcat root  69 Mar 17 11:46 startup-instance1.sh
>> -rwxr--r-- 1 tomcat root  69 Mar 17 11:59 startup-instance2.sh
>>
>
> well, there's one problem: The first 4 files have x permission for root,
> but not for the unprivileged user "tomcat" - and I hope that you're not
> starting tomcat as root. You'd look for rwxr-xr-x permission on those files.
>
> Following up on my other answer, to have both in one:
>
> root@appserver01:/opt/tomcat0# cat startup-instance0.sh
 export CATALINA_BASE=/opt/tomcat0
 cd $CATALINA_HOME/bin
 ./startup.sh

>>>
> Note that you set BASE but cd to HOME - try to see what happens by
> changing the file to
>
>echo "running as user: "
>whoami
>export CATALINA_BASE=/opt/tomcat0
>echo "cd-ing to " $CATALINA_HOME/bin
>cd $CATALINA_HOME/bin
>echo "current working directory after cd"
>pwd
>./startup.sh
>
> Note: I've copied from your file and just added some lines.
>
> report that output.
>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: I cant start Tomcat instances

2018-03-18 Thread Olaf Kock




On 17.03.2018 19:16, Loai Abdallatif wrote:

actually all of them has X permissions

-rwxr--r-- 1 root   root  70 Mar 17 11:59 shutdown-instance0.sh
-rwxr--r-- 1 root   root  70 Mar 17 11:48 shutdown-instance1.sh
-rwxr--r-- 1 root   root  70 Mar 17 11:59 shutdown-instance2.sh
-rwxr--r-- 1 root   root  69 Mar 17 11:58 startup-instance0.sh
-rwxr--r-- 1 tomcat root  69 Mar 17 11:46 startup-instance1.sh
-rwxr--r-- 1 tomcat root  69 Mar 17 11:59 startup-instance2.sh


well, there's one problem: The first 4 files have x permission for root, 
but not for the unprivileged user "tomcat" - and I hope that you're not 
starting tomcat as root. You'd look for rwxr-xr-x permission on those files.


Following up on my other answer, to have both in one:


root@appserver01:/opt/tomcat0# cat startup-instance0.sh
export CATALINA_BASE=/opt/tomcat0
cd $CATALINA_HOME/bin
./startup.sh


Note that you set BASE but cd to HOME - try to see what happens by 
changing the file to


   echo "running as user: "
   whoami
   export CATALINA_BASE=/opt/tomcat0
   echo "cd-ing to " $CATALINA_HOME/bin
   cd $CATALINA_HOME/bin
   echo "current working directory after cd"
   pwd
   ./startup.sh

Note: I've copied from your file and just added some lines.

report that output.




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: TCP6

Re: TCP6

Re: TCP6

Re: TCP6

Re: TCP6

Re: TCP6

Re: TCP6

Re: TCP6

Re: TCP6

Re: TCP6

TCP6

Re: I cant start Tomcat instances

Re: I cant start Tomcat instances

13 matches

Site Navigation

Mail list logo

Footer information