On Fri, 2006-08-11 at 09:51 +0200, Jean-frederic Clere wrote: > Rodrigo Ramele wrote: > > > 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. > > Yep. My question was: How do you decide in httpd that a JSESSIONID is > not longer valid to remove the corresponding element in your hashtable? As having this done for another project the solution is quite simple:
1. for every id in the hashtable record a timestamp/counter 2. (re)set the timecounter every time the sessionid shows up (both directions would be great - else user->server is sufficent) 3. make the sessiontimeout "managable" meaning an option in the config file. Normally the Applaction Layer Sessions have defined timeouts. Otherwise use a higher value then the Application reasonable does or as high as possible without doing too much pressure on the system. 4. the tricky part: have a) a watchdog that clears invalid sessions in idle time or b) clear sessions before looking for them (causes some performance issues) regards Klaus --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
