Session not sticky in Cluster with DirectLink

[Maximilian Weissboeck <Ma...@sphinx.at>]

We have a problem with load balancing / session stickiness when using
DirectLink.

Using Tomcat 5.0.28 in a cluster with Apache 2.0 using mod_jk 1.2.8 as
load balancer, we have the problem that an application, which uses 
DirectLink in its page is not sticky, whereas an application without 
DirectLink in its page is sticky (bound to a specific Tomcat instance). 

It seems that Apache mod_jk can not see the session info to bind the
Application to a Tomcat instance, if a DirectLink ise used. Instead
RoundRobin happens with this page.

Any hints anyone?

Thx, Max

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org

Re: Session not sticky in Cluster with DirectLink

[Kent Tong <ke...@cpttm.org.mo>]

Maximilian Weissboeck <Maximilian.Weissboeck <at> sphinx.at> writes:

> 
> We have a problem with load balancing / session stickiness when using
> DirectLink.
> 
> Using Tomcat 5.0.28 in a cluster with Apache 2.0 using mod_jk 1.2.8 as
> load balancer, we have the problem that an application, which uses 
> DirectLink in its page is not sticky, whereas an application without 
> DirectLink in its page is sticky (bound to a specific Tomcat instance). 
> 
> It seems that Apache mod_jk can not see the session info to bind the
> Application to a Tomcat instance, if a DirectLink ise used. Instead
> RoundRobin happens with this page.

Check your browser to see if it has a cookie named "JSESSIONID"
for your web app. Or better yet, capture the HTTP request to
see if the cookie is sent to mod_jk.



---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org