On 06.11.2010 12:57, Tim Funk wrote:
When running mod_jk with sticky session, but not using tomcat clustering ... Will adding a new version append the version number to the end of the session cookie AFTER the engineId (used by mod_jk for determining where to route the request)
Tried it and the jvmRoute comes last. Since it is likely that people put dots into the webappVersion, I'll add a loop to mod_jk that keeps looking for dots if it can't match the worker name to something it knows.
Since the session id tomcat generates is always all uppercase. Should the 'V' for the append be a lower case v? Even though session id collision is *rare*, but using a char that isn't in the session id name space would eliminate that problem.
The ids are actualy hex, so "V" is safe at least concrning ur own id generators. Nevertheless I also wonder whether a more obvious character would make it easier to understand (like "-" or "_"). Of course we are not safe from collissions with webappVersion characters or jvmRoute characters.
Still need to read the patch, just strated playing around with a patched trunk.
Regards, Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
