Jboss 4.2.2 Session stickiness and load balancing

[med.sami]

Mates,

I have a question regarding Treecache and sticky sessions.

I have a J2EE application which run behind a JBOSS 4.2.2 in the treecache.xml i initiate all the peers:

that's mean all nodes are discovered in the start up, if a peer is dead, new requests will be forwarded to the other available peer

<TCPPING initial_hosts="host1[27810],host2[27810],host3[27810]"

so if the host1 is note available, connections will be forwarded to node 2 and so on.

I tested and it works.

How jboss is managing the session, how to configure sessions stickiness to dispatch the request to the appropriate node (every future request from the same client will be processed by that same node, how can i define the load factor?

Actualy I was able to define sticky session only using mod_jk of apache with conbinaison of two Jboss servers to dispatch session to the available node.

Regards

[jaime.chavarriaga]

TreeCache can be used as a distributed cache. You can use it for HA deployments, including replication of session data. It is not directly related with redirecting http requests. For load balancing, you need to configure a load balancer software (e.g. mod_jk) just like you are currently doing.

If you are interested, load balancing with sticky sessions can be configured along with Buddy replication in TreeCache. You can replicate some data to all your computers, and other data not. If you are using sticky sessions, session data may be not replicated because all the web requests from the same web browser are directed to the same JBoss server.

you can review Buddy Replication configuration for TreeCache

• http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/4.2/html-single/JBoss_Cache_Tree_Cache_Guide/index.html#Clustered_Cache___Using_Replication-Buddy_Replication