Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 24815 invoked from network); 1 Mar 2005 19:16:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 1 Mar 2005 19:16:25 -0000 Received: (qmail 83426 invoked by uid 500); 1 Mar 2005 19:16:11 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 83405 invoked by uid 500); 1 Mar 2005 19:16:10 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 83390 invoked by uid 99); 1 Mar 2005 19:16:10 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from ns2.adaweb.net (HELO NS2.adaweb.net) (208.186.142.125) by apache.org (qpsmtpd/0.28) with SMTP; Tue, 01 Mar 2005 11:16:09 -0800 Received: From PELICAN.ada.net.gov ([208.186.142.115]) by NS2.adaweb.net (WebShield SMTP v4.5 MR1a P0803.345); id 1109704485263; Tue, 1 Mar 2005 12:14:45 -0700 Received: from SWAN_MAIL1.ada.net.gov ([10.113.5.241] RDNS failed) by PELICAN.ada.net.gov with Microsoft SMTPSVC(6.0.3790.211); Tue, 1 Mar 2005 12:12:14 -0700 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Subject: RE: Tomcat Cluster Date: Tue, 1 Mar 2005 12:12:00 -0700 Message-ID: <9FACF2700DF15849849992AB521FF8750244FD@SWAN_MAIL1.ada.net.gov> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Tomcat Cluster Thread-Index: AcUeeaT6Oa3zXeoZTxOk1pmGjTXFTwAFIZ/g From: "Randall Svancara" To: "Tomcat Users List" X-OriginalArrivalTime: 01 Mar 2005 19:12:14.0615 (UTC) FILETIME=[93F2D270:01C51E92] X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I used the tools that I downloaded from javagroups as described and I can send messages back and forth over multicast on 224.0.0.4 on port 45564 just fine. I am using the private address space of 10.111.22.x. My servers both contain one network card and each server defined as device eth0. Networking is working fine on each machine as I can ping to anywhere in the world. The only thing I can deduce is that I have a configuration issue that I need to figure out. =20 Just a quick check list.... 1. Uncomment cluster elements in server.xml 2. Uncomment the replication valve in server.xml.....I am assuming this is the=20 valve that is listed in the cluster element in the server.xml. 3. Set all of you session attributes to implement java.io.seriazable 4. Tomcat instances are not on the same machine, so the tcpListenPort can be the same????? 5. My web xml is set to distributable for my testapp web application. Possible problems that I have come up with include: Explicitly defining mcastBindAddress=3D"10.111.22.167" when it is not necessary. Explicitly defining tcpListenAddress=3D"10.111.22.167" when it is not necessary. I did not uncomment the correct valve?? Any thoughts/opinions on the matter would be appreciated. Randall -----Original Message----- From: Richard Mixon (qwest) [mailto:rnmixon@qwest.net]=20 Sent: Tuesday, March 01, 2005 9:16 AM To: Tomcat Users List Subject: RE: Tomcat Cluster=20 Randall, Below is the clustering section of my server.xml running under SuSE Linux (SLES9). Things to check I can think of: 1. Is your server multi-homed (more than one network adapter)? If so you "must" (at least from my experience) specify both "mcastBindAddr" and tcpListendAddress as shown below. In my case I'm using a dedicated adapter to connect the cluster over the private address space 192.168.11.x. Obviously the values are different for the Tomcat instance on each server. 2. If after reviewing this it still does not work you can test that multicasting is really working by using the utilities included in the JGroups jars. See: http://www.jgroups.org/javagroupsnew/docs/newuser/node15.html#ItDoesnt Work HTH - Richard -----Original Message----- From: Randall Svancara [mailto:rsvancara@adaweb.net] Sent: Tuesday, March 01, 2005 8:47 AM To: Tomcat Users List Subject: RE: Tomcat Cluster Apparently this was too verbose for anyone to read. I simply just don't understand why each tomcat instance is failing to recognize any other instance in the cluster. Multicast messages are being broadcasted. Is there any configuration parameter I can turn on that will verify that each tomcat instance can see the other instances??? Thanks, Randall -----Original Message----- From: Randall Svancara [mailto:rsvancara@adaweb.net] Sent: Wednesday, February 23, 2005 9:44 AM To: Tomcat Users List Subject: Tomcat Cluster I have attempted to configure a tomcat cluster using version 5.5.7 of tomcat. I have configured a simple tcp cluster in the server.xml. I have two tomcat instances installed on two different Linux servers (Fedora core 3, IPTAPLES is turned off, there is not firewall). I have apache and mod_jk set up on a third server. Multicast is enabled!!! When I start up each tomcat instance I receive the following message in the catalina.out file. ------ Feb 23, 2005 9:21:49 AM org.apache.catalina.cluster.tcp.SimpleTcpCluster start INFO: Cluster is about to start Feb 23, 2005 9:21:49 AM org.apache.catalina.cluster.mcast.McastServiceImpl setupSocket INFO: Setting multihome multicast interface to:/10.111.22.163 Feb 23, 2005 9:21:49 AM org.apache.catalina.cluster.mcast.McastService start INFO: Sleeping for 2000 secs to establish cluster membership Feb 23, 2005 9:21:51 AM org.apache.catalina.cluster.deploy.FarmWarDeployer start INFO: Cluster FarmWarDeployer started. Feb 23, 2005 9:21:51 AM org.apache.catalina.cluster.session.DeltaManager start INFO: Starting clustering manager...:/testapp Feb 23, 2005 9:21:51 AM org.apache.catalina.cluster.session.DeltaManager start INFO: Manager[/testapp], skipping state transfer. No members active in cluster group. ----- The important thing to note here is that in the last line, I see "INFO: Manager[/testapp], skipping state transfer. No members active in cluster group." At first I was thinking that multicast was not working properly. However, I was researching the Tomcat mailing list and found another thread discussing the same issue. I tried to use the tool, tomcat-replication.jar located on the CVS for tomcat. I can see the multicast sessions being generated between both servers using this tool. I also started up ethereal, the packet sniffer. I noticed that both servers are generating multicast packets. However after careful analysis of the packet information, I noticed that my servers were looking for 127.0.0.1/4001 for the receiver port. So I set the tcpListenAddress from "auto" to "10.111.22.163" This seemed to fix the problem with the multicast packets sending out the incorrect listener addresses. However, I am still getting the same error... "INFO: Manager[/testapp], skipping state transfer. No members active in cluster group." So here are my questions: 1. Is this really an error, or is session replication working and I am not testing it properly? 2.What is the proper way to test that session replication is working properly? Can anyone provide me with code that works. I am currently using a bean that I declare with --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org