Chris, Do you mean, if just the sticky session is used, tomcat clustering won't be needed?
Thanks, Raquib Hasan On Tue, Jan 28, 2014 at 12:37 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Raquib, > > On 1/28/14, 12:29 PM, Raquib Hasan wrote: > > I am not sure whether the sticky session is needed or not. The > > session replication also may not be needed. My requirement is very > > simple. > > If you don't need anything fancy, may I suggest that you start by > using sticky sessions and no session-replication? If you use sessions, > you'll need to use one of the two otherwise nothing will work properly. > > Sticky-sessions are simple to configure and get you a lot of mileage > without much horsepower at all. > > > There are 2 back end servers. I want both gets same user > > communication at the same time, so that, if one server fails the > > other can continue. > > Assuming that you can suffer the loss of a single in-progress request, > you want to route the request to a /single/ back-end server and not do > something weird like broadcasting. If you use sticky sessions, the > same back-end server will get all of the requests for a particular > session. > > If that node fails, subsequent requests will be routed to the other > server. If you don't have session-replication enabled, the user's > session will be lost and they will have to re-login, possibly > re-starting any work in-progress. That's up to your webapp's tolerance > for fail-over to handle. > > > I though cluster is the solution. Does the session replication > > come with the clustering feature? > > Clustering ≈ session replication. Tomcat's clustering does not provide > anything other than session replication. > > > VIP means Virtual IP address given to client. Back-end servers can > > be communicated using the VIP no matter where the LB routes the > > requests to. > > I don't think that's necessary at all. LBs are designed to handle sets > of back-end servers and choose one of them based on a number of > criteria. You don't need to create a virtual IP that wanders-around > through your beck-end servers: the Big IP itself is the IP address > everyone will hit. > > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > Comment: GPGTools - http://gpgtools.org > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQIcBAEBCAAGBQJS5+rxAAoJEBzwKT+lPKRYMqIP/3ekCp19upctE7XhZCu5/eca > 5DZkTqzVtBoX2twnnRAwd9CN8X2aTAo26Lg9H+KtVeykGyKx4tseycWzq/4mR1Dq > g4v8uw6SK/L7yReC84gUW55bvMxr93t4Zdy8dy6qp0L5yoEVlFEEbSaIcOyYHuIA > NbFef4Cv5v8JjOOqNSRiwuweXs2IVRRzDee26YrB5ASwP1wPIG6emlCCdlMLqjvo > eKmM1Gcm6AVoiJT+iG47Tms2MXrNhk58HD6xjh4+APdzs70/419UGVEj+YeKcMBv > 0/vu27wnZd90AECKgSwv8f0aAgkX4pveEyBf1UvvoEywZ1nEj6LLv/+1xELX/1no > pS0/cBGcDE8ujPUpa/SsLFyVkvJPcLYTdQ5V0yMUHb7qQysduYLF5mSI30OGs+aW > DJm0bzLU6XZhVofmDBnG6vpYQKH3BxMjLlsUzQdM2W2EP/NwmNZuILfWJ6P/Wc3d > r6Fck7GbAD5Ycn666FpclMIZC6H7GhlsRs9TGwRh0s3RBpQm9nLIIUiUDlRNJz3c > hOMU6FRP1COx2dNjSPATtKnT2IPKofDpWSVTrlK9PrmFG7WztMboF0dfZZFamyZD > wTzppXEXgW+scDYbnp+Nn7O55YReQfBW4Gk3qvWIgIEG6vs7wl8LRsr1a2FODCJb > VmOeh6a6RNIemYG4nxCJ > =X+/W > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
