Rainer, Jean, thank you both of you !
mod_jk already uses shared memory, but since it should >work for apache
1.3 and 2.0/2.2 it does not use apr. If your extensions are >only meant
for 2.0/2.2, then have a look at apr:
http://apr.apache.org/docs/apr/modules.html
I think I only meant it for apache 2.0/2.2 so I will check this ... at
least to reach to a working solution.
I'm not sure, that I understand your use case. Isn't Enhydra able to
include the node info in the cookie, or maybe you are able to set
another cookie with the node info, so that the balancer doesn't have to
keep state.
Exactly, Enhydra is not able to include the node info in the cookie (cannot
set something like 8FAB8...23AB.ajp13-server1 as jsessionid), so the request
is not properly redirect to the correct worker, and I cannot login.
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?
Is a good point. I suppose I could set a timestamp and keep checking it
(replicating the session timeout web.xml configuration scheme). Is there
any way I could ask the tomcat if some specific jsessionid is longer valid ?
I have created the slotmem for that (is in the httpd >branche
httpd-proxy-scoreboard).
I will check it out, thank you !!!
> Suse 9.2, Apache 2.2.3, mod_jk 1.2.15
>> >
