1 Reply Latest reply on Mar 30, 2009 9:47 AM by Suresh Reddy

    JBoss cluster: session stickiness

    Suresh Reddy Newbie

      Hi All,

      I configured Jboss 4.2.3 2 node cluster with Apache/mod_jk connector.

      The applicaion deployment (thru farm) is fine... but, I see weird behavior some times.

      1) My application is using JAAS authentication. I made modifications to 'login-config.xml' of both the nodes; When I access application thru apache port, the request is sent to both the nodes and it fails first time... on page refresh, reentering the credentials works fine.

      2) I specified session stickiness.. still my app. requests are routed to both the nodes; my understanding is, the session should be created on one node and all subsequent requests should be sent to the same.. if the node goes down, the session should be replicated on next node and requests should be routed to that.. but, the same is not happening in my case.

      here is my conf:
      Worker.properties:

      worker.node1.port=8019
      worker.node1.host=localhost
      worker.node1.type=ajp13
      worker.node1.lbfactor=1

      worker.node4.port=8039
      worker.node4.host=localhost
      worker.node4.type=ajp13
      worker.node4.lbfactor=1

      worker.loadbalancer.type=lb
      worker.loadbalancer.sticky_session=1
      worker.loadbalancer.balance_workers=node1,node4

      And Jboss xmls are modified to define 'jvmRoute'
      node1:
      < Engine name="jboss.web" defaultHost="localhost" jvmRoute="node1" >

      node4:


      I enabled
      true
      for both nodes.

      Also, I set
      true
      in web.xml

      Any pointers would be highly appreciated.

      Thanks,
      Suresh