On 05/04/2012 14:57, Dhaval Jaiswal wrote:
> Thanks for the info. We are using sticky sessions only with BackupManager.
>
> See We have the current setup.
>
> 1 Apache + sticky sessions with mod_ajp proxy balancer in httpd.conf + 10
> tomcats.
>
> currently if one of our tomcat goes down the Us
Thanks for the info. We are using sticky sessions only with BackupManager.
See We have the current setup.
1 Apache + sticky sessions with mod_ajp proxy balancer in httpd.conf + 10
tomcats.
currently if one of our tomcat goes down the User sessions goes down, I
need to stop this quickly somehow
On 21/03/2012 09:15, Dhaval Jaiswal wrote:
> We have already server.xml(changed as per tomcat site instructions)
> in place, but it is not working properly. I will give you detail idea
> about our environment.
>
> We have 10 tomcats starting from 192.168.3.1 to 192.168.3.10. I
> wanted to make 192
We have already server.xml(changed as per tomcat site instructions) in
place, but it is not working properly. I will give you detail idea about
our environment.
We have 10 tomcats starting from 192.168.3.1 to 192.168.3.10. I wanted to
make 192.168.3.10 as master/backup node, which has a session id
Take the sample from the tomcat site, change DeltaManager to BackupManager
> -Original Message-
> From: Dhaval Jaiswal [mailto:dhaval.jais...@via.com]
> Sent: Monday, March 19, 2012 4:32 AM
> To: users@tomcat.apache.org
> Cc: Shrinivas Devarkonda
> Subject: Need a sample server.xml file fo