You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Edoardo Causarano <ed...@laziomatica.it> on 2006/03/21 17:29:03 UTC
FarmWarDeployer instructions
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: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: FarmWarDeployer instructions
Posted by Edoardo Causarano <ed...@laziomatica.it>.
Alle Tuesday 21 March 2006 18:05, Filip Hanik - Dev Lists ha scritto:
Thank you Filip, please bear me one more time. I understand that only the
"tomcat cluster master" should have a watchDir configured and watchEnabled
set to true. The deployDir of all "tomcat cluster members" should point to
the clustered <Host> appBase attribute; in case the <Cluster> element is
defined on the <Service>, the directory should be the parent of the enclosed
<Host> appBase attributes. Is this correct?
The watchDir doesn't have anything to do with the appBase folders and can be
exposed using any network filesystem (eg. CIFS, DAV or NFS) as long as the
"tomcat cluster master" process can access it. Is this correct?
In order to get the farm deployment running I do not have to download the
tomcat-deployer package. Right?
If directories don't exist (especially the tempDir) will Tomcat crash and burn
or silently fail to "farm deploy"?
e
> 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: users-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: users-help@tomcat.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
------------------ Disclaimer ------------------
Ai sensi del D. Lgs. n. 196/2003, si precisa che le informazioni contenute in questo messaggio e negli eventuali allegati sono riservate e per uso esclusivo del destinatario.
Qualsiasi diffusione, distribuzione o copia della presente comunicazione non autorizzata per iscritto è severamente proibita ed espongono il responsabile alle relative conseguenze civili e penali.
Chiunque riceva questo messaggio per errore, è pregato di distruggerlo insieme agli eventuali allegati, non trattenendone copia, e di informare immediatamente Laziomatica S.p.A.
------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: FarmWarDeployer instructions
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
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: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org