Weblogic session cookie is changing primary and secondary servers -


we have weblogic set in 2 managed server cluster. requests go through load balancer (supposedly) has been configured sticky sessions. however, our requests getting bounced between managed nodes if sticky sessions not configured.

one thing noticed jsessionid cookie swapping primary , secondary server hashes. should remain same throughout life of user's session.

e.g. seeing

request 1, jsessionid=abcdefg...!server1hash!server2hash request 2, jsessionid=abcdefg...!server2hash!server1hash request 3, jsessionid=abcdefg...!server1hash!server2hash 

and seeing hash's set "none", if member of cluster no longer there:

request 4, jsessionid=abcdefg...!server1hash!none 

does know why primary , secondary servers switch this?

in cases we've come across in past, it's problem @ load balancer, not or cannot recognize session sticky server 1 , switches server 2. behaviour more pronounced @ heavy traffic.

on 1 occasion (circa 2003 on weblogic 6.1) , because cluster multicast address of pattern x.0.0.1

after long investigation bea folks, found source of problem. resulted in public bea docs being updated explicitly state

do not use x.0.0.1 multicast address x between 0 , 9, inclusive


Comments

Popular posts from this blog

asp.net - repeatedly call AddImageUrl(url) to assemble pdf document -

java - Android recognize cell phone with keyboard or not? -

iphone - How would you achieve a LED Scrolling effect? -