Hi Rainer! Thanks a lot for taking a time to answer . However i failed to explained my configuration :). I have 2 physical server each running httpd which connects (via mod_jk) to one tomcat that is running on the same host (2 tomcats). The "6" in tomcat meant to say that i have tomcat of version 6 . However you actually helped me, please see below.
No, if your load balancer does not implement session stickyness > correctly - as you noted above - you need to let both Apache servers > connect to all 6 Tomcats to be able to correct the erros done by the > load balancer. > > Do i actually have to? If my tomcat are same and the sessions are replicated then what does it metter to which one the request goes? > wA0.port=8009 > wA0.route=nodeA > wA1.port=8109 > wA1.route=nodeA > wA2.port=8209 > wA2.route=nodeA > > wB0.port=8009 > wB0.route=nodeB > wB1.port=8109 > wB1.route=nodeB > wB2.port=8209 > wB2.route=nodeB > > ... > > Thanks! The "w.route" was something that i missed. However my problem is different : I have several applications that are configured to be on different worker while those workers are on the _same_ tomcat instance ! That is because those workers use different configurations (such as timeout etc.). All the applications are in the same Engine on different Contexts . How do i configure cluster in that case? What i was thinking is that since i have one httpd for each tomcat then there is no point in setting the jvmRoute anyway.But is jvmRoute optional? Thanks again Evgeny
