only one server should have (watchEnabled="true"), this is the location
where you deploy all your files.
if you enable it on all servers, then just be careful so that you don't
deploy the same file in two locations and end up with a deployment
collission.
tempDir="/tmp/war-temp/" --> The directory the deployer uses to assemble
file transfers
deployDir="/tmp/war-deploy/" --> the directory where the deployer
deploys the WAR file to
watchDir="/tmp/war-listen/" --> the listen directory, this is where you
drop in a new file so that the deployer can pick it up
watchEnabled="false" -->true means we are watching for new deployments,
false means we act as a slave, only get deployments from other nodes.
Filip
Edoardo Causarano wrote:
Hello list,
I've managed to get a test cluster working. ATM all cluster members have their
own copy of deployed servlets and jsp pages. as well as the apache httpd
frontend that contains an unpacked copy of the war file for static file
serving.
The current config is awkward to maintain but apparently the
org.apache.catalina.cluster.deploy.FarmWarDeployer class takes care of
replicating the wars across the cluster.
Ideally (unlesss I don't have a clue) the apache cluster lead has a tomcat
running in JNI mode where deploys are performed. The other tomcat only
cluster members are notified of the new deployment and get their local copy
syncronized. Does tomcat sync on the multicast channel or must I export the
lead's webapps dir on NFS and point the other members' watch dir to it?
Can anyone post their (sanitized) config so I can get the gist of it?
Thanks,
e
(btw, yesterday it wouldn't work because one of the two test machines didn't
have mcast in the kernel... grrr....)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
