1 Reply Latest reply on Mar 7, 2004 4:38 AM by derry

    Apache2,mod_jk2,jboss3.2.3/Tomcat41 - ONLY sticky session lo

    dhartford

      Hey all,
      After going through all the posts, I'm still a little hazy on why I still can not setup simple load-balancing WITH sticky sessions based on the environment above (and also referenced the pay-for Clustering doc).

      1. Is there a sticky_session or stickySession flag for mod_jk2 in the workers2.properties file?

      2. Is it required to change the TomcatSAR jboss-service.xml to add in a jvmRoute to the following default fragment: { }?

      3. What else may be missing? This looks trivial as a lot of people have put in some good work to make it so, but must be something I'm missing somewhere as the 'sticky session' just is not working.

      (1) Apache2.0 w/mod_jk2
      (2) Jboss3.2.3 Default w/standard embedded tomcat41

      Thanky!
      -D

        • 1. Re: Apache2,mod_jk2,jboss3.2.3/Tomcat41 - ONLY sticky sessio
          derry

           

          "dhartford" wrote:
          Hey all,
          2. Is it required to change the TomcatSAR jboss-service.xml to add in a jvmRoute to the following default fragment: { <Engine name="MainEngine" defaultHost="localhost"> }?


          Go to {jboss_home}/server/default/deploy/jbossweb-tomcat50.sar. Edit server.xml. Add jvmRoute to the Engine-tag.

          CU
          Thomas