I've my application located in weblogic 8.1 cluster and that i have 2 nodes during my cluster. We use CAS that is in tomcat 6 to authenticate towards the weblogic application. There exists a Apache 2.2.3 webserver acting like a reverse proxy/loadbalancer and does stick session. Presently using the below configuration the session stickness occurring. My Requirement is the fact that each time a user access my application located in weblogic the session should use any of the node and all sorts of the request ought to be servered with that particular node. Suppose in the event that node fails the session ought to be duplicated towards the secondary node without losing session. Below is my configuration.
##weblogic## <VirtualHost *>`enter code here` ServerName web.qa.xx.com ServerAlias web ProxyPass / balancer://mycluster/ stickysession=JSESSIONID nofailover=On ProxyPassReverse / https://web.qa.xx.com/ <Proxy balancer://mycluster> BalancerMember http://node1.qa.xx.com:7701 route=node1 BalancerMember http://node2.qa.xx.com:7701 route=node2 </Proxy> ErrorLog /var/httpd/web.log </VirtualHost> ##tomcat### <VirtualHost *> ServerName cas.qa.xx.com ServerAlias cas ProxyPass / balancer://cascluster/ stickysession=JSESSIONID nofailover=Off <Proxy balancer://cascluster> BalancerMember http://cas1.qa.xx.com:443 route=cas1 BalancerMember http://cas2.qa.xx.com:443 route=cas2 </Proxy> ErrorLog /var/httpd/cas.log