i'm not sure if this is a similar issue to this thread, but i setup a 3 member tomcat cluster on 1 machine the other night (ensuring that ports were unique) and also each AJP was unique and so fourth. jk was configured correctly.
i noticed on starting each tomcat, that although it seemed happy to startup with the cluster configuration, it output that no other members were detected at that point. All 3 tomcats reported no other members, although each were convinced they were a member of their own cluster. i have no logging with me here, but just in case this is the same thing .. sounds simialr. I was using 5.5.4 Allistair. > -----Original Message----- > From: Filip Hanik - Dev [mailto:[EMAIL PROTECTED] > Sent: 06 December 2004 14:41 > To: Tomcat Users List > Subject: Re: another problem with session replication > > > This should work fine. What do your logs say? > > Filip > > ----- Original Message ----- > From: "Ina Skåre" <[EMAIL PROTECTED]> > To: "Tomcat Users List" <[EMAIL PROTECTED]> > Sent: Monday, December 06, 2004 8:36 AM > Subject: another problem with session replication > > > Thank you for your quick response, Filip, you saved me a lot of hassle > trying to figure out the problem... > I have now discovered another issue. When restarting tomcat, > my application > joins the cluster and receives all the mcast messages from > that point on, > but does not receive the state at startup (so attribute must > change before a > notification is send and the new member receives any > messages). Do you have > any idea whats going on here? > > Thank you , > Ina!. > > > ----- Original Message ----- > From: "Filip Hanik - Dev" <[EMAIL PROTECTED]> > To: "Tomcat Users List" <[EMAIL PROTECTED]> > Sent: Monday, December 06, 2004 3:00 PM > Subject: Re: problems with session replication > > > > yes, this is a known bug. Should be fixed in .29 or .30. > > > > Filip > > > > ----- Original Message ----- > > From: "Ina Skåre" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Monday, December 06, 2004 6:47 AM > > Subject: problems with session replication > > > > > > Hi, > > I'm a newbie to tomcat session replication. I have a web application > > running on several tomcat instances (5.0.28) in a clustered > > environment. Session replication is working as it should > when stopping and > > restaring a tomcat instance. The member joins the cluster > > and receives all mcast messages from the other members. But > when stopping > > and restarting the web application using tomcat manager > > without stopping tomcat itself, the new cluster member is > not rejoining > > the cluster at all and receives no session state or mcast > > messages. What can be the problem. It would be great if > someone could > > point me in the right direction. > > > > Thank you! > > Ina > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > <FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE> ------------------------------------------------------- QAS Ltd. Developers of QuickAddress Software <a href="http://www.qas.com";>www.qas.com</a> Registered in England: No 2582055 Registered in Australia: No 082 851 474 ------------------------------------------------------- </FONT> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
