also forgot to mention, setting TTL on the multicast will keep the multicast messages from going all over the place
Filip -----Original Message----- From: Filip Hanik (lists) [mailto:[EMAIL PROTECTED] Sent: Friday, September 03, 2004 7:53 PM To: Tomcat Users List Subject: RE: Tomcat 5.5 In-Memory Session Replication Make sure you have multicast enabled. This can be a little tricky if you run on a multihomed host, but you can google it. >The only thing I see logged is the message: If it says skipping state transfer, no other members in the cluster, means that the members haven't discovered each other, this goes back to making sure your multicasting is working. In the log you will see that members are joining the cluster when it is working >What prevents a "hostile" tomcat >instance from joining the cluster when the cluster are you kidding me, there are no "hostile" tomcats, only "friendly" ones. (slap yourself on the head if you configure tomcats on the same multicast address but you don't want them to be in the same cluster, after a few times, you'll have it figured out :) Filip -----Original Message----- From: Tomcat Newbie [mailto:[EMAIL PROTECTED] Sent: Friday, September 03, 2004 6:27 PM To: Tomcat Users List Subject: Tomcat 5.5 In-Memory Session Replication I know the replication subject has been addressed somewhat for 5.x. I am trying my first replication setup with two 5.5 servers on the same host. Each Tomcat instance works just fine by itself. I followed the configuration notes for Tomcat in the documentation for in-memory replication, however I do not see any activity in the logs as far as replication is concerned. The only thing I see logged is the message: Sep 3, 2004 6:59:37 PM org.apache.catalina.cluster.session.DeltaManager start INFO: Starting clustering manager...:/servlets-examples Sep 3, 2004 6:59:37 PM org.apache.catalina.cluster.session.DeltaManager start INFO: Manager[/servlets-examples], skipping state transfer. No members active in cluster group. The two instances are setup with unique tcpListenPort properties. The application has <distributable /> in web.xml on both instances. I tried the setup with both dirtyFlag enabled and disabled. I even tried to put it behind Apache server proxy to get rid of localhost:port, but it has not changed anything. I still see no session replication activity. Each instance creates its own sessions and they are not propagated. Can someone offer some ideas as to how to proceed? Also, a couple of questions regarding the replication. What prevents a "hostile" tomcat instance from joining the cluster when the cluster is configured on multiple hosts? Is there any documentation on replication using JDBC--I saw it mentioned, but no examples or configuration options. Thanks, Ed --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.740 / Virus Database: 494 - Release Date: 8/16/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.740 / Virus Database: 494 - Release Date: 8/16/2004 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.740 / Virus Database: 494 - Release Date: 8/16/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.740 / Virus Database: 494 - Release Date: 8/16/2004 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
