-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sam,
Shamshad Ansari wrote: | I have a web application which runs on Tomcat. There will be at any | given time a maximum of 20 users. So, the traffic is not much. | However, the application is kind of mission critical and therefore, we | can not afford any downtime. I am thinking Clustering would be an | option where if one server goes down, the other picks up. Is it acceptable for users to have to re-login in the event of a server failure? If so, you can just set up simply clustering via mod_jk, which binds a particular session to a single back-end machine. You don't have to use distributable sessions or worry about sending data around the cluster so the data is available everywhere just in case a server goes down. | Could any one please suggest what would be the best option. Also, if | you could point me to a good tutorial to accomplish this. may be a | step-by-step example. You should definitely start here: http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html There is quite a bit of information in there, including background info and step-by-step instructions. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkhf0SIACgkQ9CaO5/Lv0PB5nACfaGFZgtF+CX1OMH96jAB5DOh8 A+wAmwcr/WX6QMn5DqhahKRO0tb9QGMK =imH8 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
