2015-09-08 15:51 GMT+02:00 Jeffrey Janner <jeffrey.jan...@polydyne.com>: >> -----Original Message----- >> From: Christopher Schultz [mailto:ch...@christopherschultz.net] >> Sent: Friday, September 04, 2015 12:46 PM >> To: Tomcat Users List <users@tomcat.apache.org> >> Subject: Re: Multiple JSESSIONID cookies being presented. >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA256 >> >> Jeffrey, >> > Now, it's been doing this since at least Tomcat 6, I have one running now, > and I've never had a problem with it using direct connections. But now we > are front-ending with HaProxy and going to two backend tomcats, and using the > JSESSIONID to support sticky-sessions. I'm afraid the multiple cookies is > confusing HaProxy. (Yes, I'm going to ask that user community.) > Jeff
You could use another cookie to implement stickyness "You can add a cookie SOME-COOKIE-NAME prefix directive into the backend. Then simply add the cookie directive within each server. Then HAProxy will append a cookie (or add onto an existing one) a identifier for each server. This cookie will be sent back in subsequent requests from the client, letting HAProxy know which server to send the request to. This looks like the following:" backend nodes # Other options above omitted for brevity cookie SRV_ID prefix server web01 127.0.0.1:9000 cookie check server web02 127.0.0.1:9001 cookie check server web03 127.0.0.1:9002 cookie check https://serversforhackers.com/load-balancing-with-haproxy --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
