can't answer for how the "stickyness" works in mod_jk, but there are some docs on it
Filip > -----Original Message----- > From: Jan Agermose [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 09, 2003 11:10 AM > To: Tomcat Users List > Subject: Re: Tomcat 5 clustering > > > well yes, thats a point :-) apache will forward a session to a new host if > the host that first "owned" the session (in a sticky sense) fails? Will > apache be aware of a tomcat instance getting back online and start reusing > it for requests? Of cause, I guess... I will have to start looking into > this - and using it :-) > > Jan > > > ----- Original Message ----- > From: "Filip Hanik" <[EMAIL PROTECTED]> > To: "Tomcat Users List" <[EMAIL PROTECTED]> > Sent: Tuesday, September 09, 2003 8:01 PM > Subject: RE: Tomcat 5 clustering > > > > yeah, clustering (session replication) will only gain you fail over and > high > > availability, not performance > > > > Filip > > > > > -----Original Message----- > > > From: Jan Agermose [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, September 09, 2003 10:26 AM > > > To: Tomcat Users List > > > Subject: Re: Tomcat 5 clustering > > > > > > > > > well I cannot really say I have a problem.. I'm not using clustering - > yet > > > :-) > > > > > > But I am somewhat interested in the performance of this... What I mean > is, > > > if You have sticky session You do not really cain anythink from > > > ditributing > > > the session, now do you? That looks like a performance hit > for nothing? > > > > > > And since im not that big a fan of using something like www1, www2 and > so > > > on... Am I out of options? How can I take advantage of this??? > > > > > > I guess my problem is I need some insigt on how to supercharge my > > > applications :-) > > > > > > jan > > > > > > > > > ----- Original Message ----- > > > From: "Filip Hanik" <[EMAIL PROTECTED]> > > > To: "Tomcat Users List" <[EMAIL PROTECTED]> > > > Sent: Tuesday, September 09, 2003 6:12 PM > > > Subject: RE: Tomcat 5 clustering > > > > > > > > > > not sure what your problem is Jan, > > > > the clustering code is all-to-all node replication, so whether you > have > > > > sticky sessions or round robin loadbalancing, it will work > > > > > > > > Filip > > > > > > > > > -----Original Message----- > > > > > From: Jan Agermose [mailto:[EMAIL PROTECTED] > > > > > Sent: Tuesday, September 09, 2003 6:50 AM > > > > > To: Tomcat Users List > > > > > Subject: Re: Tomcat 5 clustering > > > > > > > > > > > > > > > ok but how would you use it... > > > > > > > > > > If you have apache in front of the different tomcat instances, > > > > > apache would > > > > > route the same browsersession to the same tomcatinstance on each > > > > > request, or > > > > > not? This would make session sharing useless? > > > > > > > > > > And if there's no webserver in front you need different > domainnames - > > > lige > > > > > www, www1, www2 ??? or?? different domainnames suck :-D > > > > > > > > > > Jan > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > From: <[EMAIL PROTECTED]> > > > > > To: <[EMAIL PROTECTED]> > > > > > Sent: Tuesday, September 09, 2003 3:36 PM > > > > > Subject: Re: Tomcat 5 clustering > > > > > > > > > > > > > > > > > Jan Agermose wrote: > > > > > > > > > > > > > >> I'm not using version 5 but was looking for > information on what > > > > > > >> clustering capabilities that where build into tomcat > 5 - but I > > > cannot > > > > > > >> find anything on the webpage... looking in the wrong > places :-) > > > > > > >> > > > > > > >> Could you offer any links? Is it simply a distributed session > > > > > > >> implementation or?! > > > > > > > > > > > > > > I don't know much about it. Basically, it's a simple > > > multicast based > > > > > > > session replication implementation, written by Filip > > > Hanik (you may > > > > > > > remember his TC 4 clustering article). There are > indeed no docs > > > about > > > > > > > that at the moment. > > > > > > > > > > > > > Remy is right... (of course :) ) > > > > > > Tomcat 4.1 backport consists of a single patch as a jar file, > > > > > it uses the > > > > > > universal good library for replication (the same as Jboss > > > uses for EJB > > > > > > clustering)..Works well but requires a little knowledge of > > > > > networking (UDP > > > > > > & so on)... > > > > > > > <ad>For more complete clustering, there's JB, of > course :)</ad> > > > > > > :) > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > 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] > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
