I'm setting up session replication in tomcat 5.0.30, using apache 2.0.52 with jk 1.2.8 as the LB mechanism.
I'm currently failing to get sessions to stick to a tomcat instance. I used this article for a reference: http://www.javaworld.com/javaworld/jw-12-2004/jw-1220-tomcat.html But the author is doing it with jk2, and hasn't updated his article for jk config yet. He references the jvmRoute="servername" variable which needs to match a like variable "tomcatId" in workers2.properties. Of course workers.properties doesn't have the tomcatId variable. The funny thing is in the change notes for the jk connector, I see that Bill Barker made some change referencing the jvmRoute variable: "Check all JSESSIONID cookies for a valid jvmRoute. If you have multiple Tomcats with overlapping domains, then you can get multiple cookies without a defined order. This will route correctly as long as the different domains don't have any Tomcats in common. (billbarker)" So I infer that somehow jvmRoute is now relevant in the jk conector, and if so there might be some need for a matching tomcatId variable. What is the syntax for these variables in the jk 1.2.8 world, and where do they go? (I am assuming jk2.properties does not exist) Current file syntax: <Workers.properties> worker.list=ajp13 worker.ajp13a.port=8009 worker.ajp13a.host=localhost worker.ajp13a.type=ajp13 worker.ajp13a.lbfactor=50 worker.ajp13b.port=8010 worker.ajp13b.host=localhost worker.ajp13b.type=ajp13 worker.ajp13b.lbfactor=50 worker.ajp13.type=lb worker.ajp13.balance_workers=ajp13a,ajp13b --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
