Hello Jean, ! Thanks for answering....I didn't explain myself very well. I meant: I need to keep track each one of the JSESSIONID and the worker where the 'Set-Cookie' header comes from, so when a new Request with this cookie arrives again (from the browser) i would properly redirect it to the correct worker, where the tomcat that created this cookies is connected. It is impossible for me to use sticky_session or session replication, because I am using an Enhydra Framework inside Tomcat and it handles the session itself. So, I need some kind of "Spanning Tree" scheme. Now I am using the file system to store the hashtable and I want to know if I could use some kind of shared memory inside Apache ...
On 8/10/06, Jean-frederic Clere <[EMAIL PROTECTED]> wrote:
Rodrigo Ramele wrote: > Hello Tomcat dev: > > Suse 9.2, Apache 2.2.3, mod_jk 1.2.15 > > I am changing the way mod_jk transfer request to different workers > (tomcat > instances) in a balanced worker keeping track of the link between session > and worker, and I need to use some kind of shared memory inside mod_jk. How do you decide to that a session has timeout? (Guessing that session means jsessionid identified sessions). Cheers Jean-Frederic > (I > need to share a hashtable). Could you please give me a clue on which > set of > Apache API calls I could use to do it ? > > Thank you very much !!!! > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
