Hey,
the current FarmWarDeployer is only support development.
Active redeployment inside a cluster is very dangerous. You can have
problemes with different versions of classes or the classloader not free
all classes. My strategie is:
setup a new catalina.base.
Start the new generation servers
setup the new nodes at the mod:jk config
switch the old generation workers too disable state at mod_jk config.
Restart apache graceful.
After no sessions are active, you can shutdown the old nodes and
cleanup the mod:jk config.
Peter
Kim Brianne Go schrieb:
I'm just new to HA environments, we were able to do Apache / Tomcat Load
Balancing through AJP13. Though there were few concerns on fail overs and
session information, so we tried clustering tomcat servers. Everything went
well and working as of the moment, I know that clustering is just like
playing with fire. Without extensive knowledge could be detrimental
overtime. May I ask anybody who's implemented such architecture for a best
practices guide for this with the utilization of Farmwardeployer.
Small concern on farmwardeployer, if the farmwardeployer server went down
and was started up again. It always reloads all the application on the
watchedDir path to the entire cluster. Is this normal, or we can do
something about this to avoid such delays.
Thanks!
--
Kim Brianne Go
Customer Engineer
GBBTech Systems Incorporated
Raffles Corporate Center
9/F Emerald Avenue,
Pasig City, Philippines
Tel. No.: +63 2 9105411 to 16 loc. 104
Fax No.: +63 2 9105418
Cel No.: +63 917 8314366
Email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
