-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Martin,
On 2/21/13 8:11 AM, Martin Knoblauch wrote: > this is more of a principal question. We operate the following > HA/Failover Setup: > > Frontend: Apache 2.2.21 + mod_jk 1.2.32 Backend: 6 x Tomcat 7.0.32 Sticky sessions or not? > We can have the users look at the jvmroute part of the session > cookie. > > The problem arises on the batch clients. How to ask them? :-) So, > the question is whether there is a way of finding out from the > outside which tomcat a client-session is talking to? The > connections are of course all through the Apache frontend, which > does not make it easier. How can you identify a client in general? Do they maintain sessions? If so, how do they maintain them (e.g. cookie-based, URL-based, or no session state)? Obviously, if there is no session state, then there is no "backend serving them" because they'll just use whatever backend they get for their individual requests. > Any insight (or pointer to the right manual) would be highly > appreciated. > > Ah yes, modifying the application to just log the cookie is of > course possible, but for reasons, not to be discussable here, > political difficult. How about modifying the clients? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEAREIAAYFAlEmcpsACgkQ9CaO5/Lv0PCIJACfZq8Q79yiIeu8dN01ApTM/ciq KD0AnikzRUHmaMv4n/38dqHnjIsbc+Dt =QB9S -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
