You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Edoardo Causarano <ed...@laziomatica.it> on 2006/03/20 17:15:51 UTC

Questions on Clustering

Hello list, I have some questions on Tomcat 5.5.15 clustering. The apache 
httpd server connects to the cluster members with mod_jk. All the cluster 
members have the jvmRoute attribute set to the same value "cluster" as well 
as the same multicast group. Multicast routes are activated on the 
appropriate network interfaces with the command:
route add -net 224.0.0.0 netmask 240.0.0.0 dev eth1

On the server logs I get these messages:
1616281 [Cluster-MembershipSender] DEBUG 
org.apache.catalina.cluster.mcast.McastService  - Mcast send ping from member 
org.apache.catalina.cluster.mcast.McastMember[tcp://127.0.0.2:4001,catalina,127.0.0.2,4001, 
alive=100]
1616282 [Cluster-MembershipReceiver] DEBUG 
org.apache.catalina.cluster.mcast.McastService  - Mcast receive ping from 
member 
org.apache.catalina.cluster.mcast.McastMember[tcp://127.0.0.2:4001,catalina,127.0.0.2,4001, 
alive=1612675]

I'm a bit surprised by the loopback addresses... does this mean that the 
server is only reading itself on the multicast group?

How can I verify that the cluster members are properly acting in sync? Must 
the directories for temporary deployment exist BEFORE launching Tomcat?

Thank you,
e

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


Re: Questions on Clustering

Posted by Edoardo Causarano <ed...@laziomatica.it>.
Thanks Filip...

e

Alle 17:30, lunedì 20 marzo 2006, Filip Hanik - Dev Lists ha scritto:
> you have several problems:
>
> 1. jvmRoute should be a unique value on each tomcat, not the same across
> all.
> 2. you have used (tcpListenAddress="auto") - what this does, is look up
> your hostname, and then resolves that to an IP address.
>    The problem on your computer is that your local hostname resolves to
> 127.0.0.1, it should resolve to the computers actual IP address.
>    You can either hardcode your IP in the tcpListenAddress attribute or
> you have to fix your /etc/hosts (and any other file that is not
> configured correctly) file to not resolve your computer name to localhost
>
> Filip

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


Re: Questions on Clustering

Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
you have several problems:

1. jvmRoute should be a unique value on each tomcat, not the same across 
all.
2. you have used (tcpListenAddress="auto") - what this does, is look up 
your hostname, and then resolves that to an IP address.
   The problem on your computer is that your local hostname resolves to 
127.0.0.1, it should resolve to the computers actual IP address.
   You can either hardcode your IP in the tcpListenAddress attribute or 
you have to fix your /etc/hosts (and any other file that is not 
configured correctly) file to not resolve your computer name to localhost

Filip


Edoardo Causarano wrote:
> Hello list, I have some questions on Tomcat 5.5.15 clustering. The apache 
> httpd server connects to the cluster members with mod_jk. All the cluster 
> members have the jvmRoute attribute set to the same value "cluster" as well 
> as the same multicast group. Multicast routes are activated on the 
> appropriate network interfaces with the command:
> route add -net 224.0.0.0 netmask 240.0.0.0 dev eth1
>
> On the server logs I get these messages:
> 1616281 [Cluster-MembershipSender] DEBUG 
> org.apache.catalina.cluster.mcast.McastService  - Mcast send ping from member 
> org.apache.catalina.cluster.mcast.McastMember[tcp://127.0.0.2:4001,catalina,127.0.0.2,4001, 
> alive=100]
> 1616282 [Cluster-MembershipReceiver] DEBUG 
> org.apache.catalina.cluster.mcast.McastService  - Mcast receive ping from 
> member 
> org.apache.catalina.cluster.mcast.McastMember[tcp://127.0.0.2:4001,catalina,127.0.0.2,4001, 
> alive=1612675]
>
> I'm a bit surprised by the loopback addresses... does this mean that the 
> server is only reading itself on the multicast group?
>
> How can I verify that the cluster members are properly acting in sync? Must 
> the directories for temporary deployment exist BEFORE launching Tomcat?
>
> Thank you,
> e
>
> ---------------------------------------------------------------------
> 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