AW: [us...@httpd] Sticky sessions with Apache and Tomcat

Did you check the session cookie in your browser? There should be one and it must end with either .jvm1 or .jvm2. If there is no session cookie, maybe your application didn't yet start a session - e.g. static html pages are served w/o a session. Cheers Jürgen -Ursprüngliche

AW: AW: [us...@httpd] mod_proxy_balance: route redirect not working

I checked mod_jk today, but unfortunately it doesn't contain any management interface (like e.g. balancer-manager), so I decided to patch the mod_proxy_balancer module to add a starvation feature. I mainly added a new status (PROXY_WORKER_STARVATION) which can be chosen from balancer-manager

AW: [us...@httpd] mod_proxy_balance: route redirect not working

Owen, what exactly does labelled mean? Can I think of it in our case as the request having a cookie JSESSIONID=numbers.tomcat1, i.e. a suffix matching one of the configured workers? If so, we completely misinterpreted the meaning of redirect. We are looking for a way to starve an instance:

AW: [us...@httpd] mod_proxy_balance: route redirect not working

Owen, thanks for your answers. The balancing stuff is documented very sparsely. Does anyone have an idea of what this feature is about? Seems to be some kind of dedicated failover strategy, but I can't imagine a use case for that. Cheers Jürgen -Ursprüngliche Nachricht- Von: Boyle

AW: [us...@httpd] mod_proxy_balance: route redirect not working

André, thanks for your suggestion. I was using mod_jk a while ago, but was persuaded to switch to mod_proxy. I'm going to build a test env with mod_jk by the end of this week and keep you informed. Cheers, Jürgen -Ursprüngliche Nachricht- Von: André Warnier [mailto:a...@ice-sa.com]