Kyle,
I'm using WAS 4.0. I'm observing session affinity only while using persistent sessions.
Ok so I understand in WAS 3.5, session affinity was related to session persistence, and that behavior has apparently changed in 4.0. Tracing through the plugin log, it seems like there is a bug where it is unable to correctly parse the JSESSIONID cookie value(and hence the cloneid) from the returned cookies. I also verified this by turning off cookies from the browser and relying solely on explicit URL re-writing. In that case, everything works fine.
Has anyone experienced anything similar?
Just one more thing. Seems like the
documentation for Websphere 4.0 AE at the infocenter has not been updated since it incorrectly says that session affinity can only be achieved by using persistent sessions.
[ March 12, 2002: Message edited by: Junaid Bhatra ]