Sorry for the inconvenience. I sent the email with wrong content. An example: Machine 1: Tomcat A App1 App2 Tomcat B App3 App4
Machine 2: Tomcat C App1 App2 Tomcat D App3 App4 Using session affinity, if I make a request to App1 and the Tomcat A in Machine 1 is selected. All the sequent requests will be redirected (within the same session) to the same Tomcat (tomcat A). However, if i make a request to App3, Tomcat B (machine 1) or Tomcat D (machine 2) could be selected. What I really want is that the request to App3 could be done to Tomcat B in machine 1 (the request was done using the same browser client). Thanks On Mon, Nov 22, 2010 at 11:23 PM, Andrew Hole <andremailingl...@gmail.com>wrote: > An example: > Machine 1: > Tomcat A > > Tomcat B > > > On Mon, Nov 22, 2010 at 11:05 PM, André Warnier <a...@ice-sa.com> wrote: > >> Andrew Hole wrote: >> >>> No... Session affinity (jvmRoute in JSESSION ID) implies sending to the >>> same >>> tomcat instance (same JVM), not for the same machine. >>> >>> I guess that I still don't get it. >> The same Tomcat instance /is/, per definition, on the same machine. >> >> Or do you want to send the request to a /different/ Tomcat instance, but >> only one which is on the same machine ? And if yes, why would you want to do >> that ? >> >> In other words, why would you /not/ want to send the request to the same >> Tomcat on the same machine ? >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> >
