RE: Problem with sticky session in Tomcat4.1.18 and Apache 2.0.43 using mod_JK Connector.

2003-03-10 Thread Roberts, Eric
Filip's memory is correct. In server.xml you need an entry on the engine element: Engine jvmRoute=tomcat1 . then on the next instance Engine jvmRoute=tomcat2 etc. and your workers.properties file should declare workers tomcat1, tomcat2, etc Regards Eric -Original

RE: Problem with sticky session in Tomcat4.1.18 and Apache 2.0.43 using mod_JK Connector.

2003-03-10 Thread Joshua Sunil Kumar
Hi I check out in the server.xml there is no entry for jvmRoute. There is something called jmvRoute is it a typo or something cos I corrected it to jvmRoute and it still does not work Engine name=Standalone defaultHost=localhost debug=0 jmvRoute=jvm1 This is tag directly taken from server.xml in

RE: Problem with sticky session in Tomcat4.1.18 and Apache 2.0.43 using mod_JK Connector.

2003-03-10 Thread Roberts, Eric
There is a typo in the server.xml - it should be jvmRoute. The worker.list in your workers.properties appears to only contain the loadbalancer: #worker.list=tomcat1,tomcat2,loadbalancer worker.list=loadbalancer #worker.list=loadbalancer Uncomment the top line and remove the rest. Are you

RE: Problem with sticky session in Tomcat4.1.18 and Apache 2.0.43 using mod_JK Connector.

2003-03-10 Thread Joshua Sunil Kumar
Hi I tried correcting the typo but it does not work .Infact the load balancing itself doesn't work if I change it to jvmRoute. BR Joshua -Original Message- From: Roberts, Eric [mailto:[EMAIL PROTECTED] Sent: Monday, March 10, 2003 2:52 PM To: Tomcat Users List Subject: RE: Problem with

RE: Problem with sticky session in Tomcat4.1.18 and Apache 2.0.43 using mod_JK Connector.

2003-03-10 Thread Roberts, Eric
Joshua, Here are the extracts from my conf files. I am running Apache 2.0.43 with mod_jk and Tomcat 4.1.18 also, so please check carefully that you have similar. workers.properties: worker.list=tomcat1,tomcat2,loadbalancer worker.tomcat1.port=9019 worker.tomcat1.host=myhost

RE: Problem with sticky session in Tomcat4.1.18 and Apache 2.0.43 using mod_JK Connector.

2003-03-10 Thread Joshua Sunil Kumar
Hi Eric Thanx for the config files it works now. The only difference was the jvmRoute in the server.xml. There was a typo error in the server.xml file. Bye Joshua -Original Message- From: Roberts, Eric [mailto:[EMAIL PROTECTED] Sent: Monday, March 10, 2003 3:37 PM To: Tomcat Users List

RE: Problem with sticky session in Tomcat4.1.18 and Apache 2.0.43 using mod_JK Connector.

2003-03-10 Thread Joshua Sunil Kumar
Hi The sessiion problem has been fixed but I am getting the following error something with the JMX Bean I commented out the code for the JMX Bean in the server.xml bcos in one of the posts I found the JMX BEan and the Apj13 cannot be used together. But now I am getting these errors.

RE: Problem with sticky session in Tomcat4.1.18 and Apache 2.0.43 using mod_JK Connector.

2003-03-09 Thread Filip Hanik
BlankI remember there being a property called jvmRoute in the server.xml file that would allow the Apache workers to make sure you got the right Tomcat server upon the next request. otherwise, you can just cluster enable your system, and it should work for you.