Hey,
The jvm route is set automatically through both the ajp12 and ajp13 request handler. As example, I will take the org.apache.tomcat.service.connector.Ajp13ConnectorRequest. This class extends RequestImpl, which implements Request. For each incoming request to apache, the load balancing worker encodes the jvm route in the ajp13 requst and sends it to tomcat. Tomcat handles the request, and extracts the jvm route and sets it in the Ajp13ConnectorRequest. The Request object that you get in your jsp/servlet is actually the Ajp13ConnectorRequest. Ofcourse, I'm not 100% positive of this, but this is what it looks like to me. Please correct me if I am wrong.
Is this what you wanted to know?
-----Original Message-----
From: Mathias Herberts [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 12, 2001 12:33 PM
To: Jord Sonneveld
Subject: Re: Tomcat 3.2.1 load balancing with mod_jk
Hi,
this is what I understood of the load balancing process in mod_jk. What I could not figure out in the first place was how the Jvm Route infor
was set up in Tomcat. But I found that by writing a very simple
Interceptor I could set the JvmRoute field of each request as it came in
and therefore force the generated session IDs to be suffixed with the
route therefore bootstraping the sticky session process.
Mathias.
--
Ce message et toutes les pieces jointes (ci-apres le "message") sont
confidentiels et etablis a l'intention exclusive de ses destinataires.
Toute utilisation ou diffusion non autorisee est interdite. Tout
message etant susceptible d'alteration, l'emetteur decline toute
responsabilite au titre de ce message s'il a ete altere, deforme ou
falsifie.
-----------------------------------
This message and any attachments (the "message") are confidential and
intended solely for the addressees. Any unauthorised use or
dissemination is prohibited. As e-mails are susceptible to alteration,
the issuer shall not be liable for the message if altered, changed
or falsified.
