Sticky problem with cookies on multiple servers

Unanswered Question

We have the following general architecture:

Browser--> SecurityProxy(Auth) --> CSS (ssl frontend and backend) --> oneof[BEA ServerA1-A4 on machineA which use JSESSIONID_cookienameA, BEA ServerB1-B4 on machineB with JSESSIONID_cookienameB).


Not an unreasonable requirement. But we find that the stickiness is not retained across the two machines.

i.e., first accessing a url-A on machineA we stick to ServerA2 (e.g.), then accessing a url-B on machineB we stick to ServerB3(e.g.), however, reaccessing url-A, we are sent to ServerA3 on machineA, even though the browser and security proxy are faithfully forwarding both the cookies.


The sticky parameters are:

advanced-balance cookies

string prefix "def_clus_JSESSIONID="

string eos-char ";"

string operation hash-crc32

no persistent


Any help is appreciated. Thanks.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
s.jankowski Thu, 08/02/2007 - 12:45

Use arrow point cookies. If the cookie generated by the server is static, you can configure the CSS to look for

this cookie by configuring the content rule with the "advanced-balance cookies" parameter and configuring the services with "string " paramter.

Actions

This Discussion