Ta, for the quick reply. Okay, so I added the changes you suggested,
but to no joy. Problem is still persisting.
I believe, I can't remember really, I added route=node01 to the
balancer config so it would know which member to send the request to
based on the JSESSIONID.nodename, but it may very well be useless or
wrong. Anyhow removing it did not have the desired effect. i've double
checed the server.xml on tomcat to ensure the node name is set in the
jvmRoute and it is all fine.
The Web Dev bar in firefox points out something interesting. Other
cookies being set on the page (Google analytics etc) indicate the host
as .www.foo.com, the JSESSIONID cookie however is just www.foo.com as
in no leading period. I wonder if that is affecting it? However I
don't think so.
This really has me stumped. all the examples I can find on the net all
indicate that this should work with just the ProxyPassReverse
directive, the balancer URL and the stickysession.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!