- Original Message -
> From: Marco Betti
> To: Tomcat Users List
> Cc:
> Sent: Friday, October 21, 2011 7:18 AM
> Subject: Re: FarmWarDeployer undeploy on slave node when tomcat restart
>
> Hi Keiichi,
> many thanks for your suggestion.
> By setting synchro
Hi Keiichi,
many thanks for your suggestion.
By setting synchronous replication everything works.
Unless processing updated war by one message, I think that async replication
shouldn't be used (personal opinion).
By the way I wander If asnyc replication couldn't lead to some other
unexpected behavi
I checked FarmWarDeployer's code.
When WAR is updated, FarmWarDeployer sends UndeployMessage and sends
FileMessage after that.
The node which received UndeployMessage undeploys war.
The node which received FileMessage deploys war.
If FileMessage is received while processing UndeployMessage, the
fo
Tried also on Tomcat 7.0.22
Same behaviour: when i restart node1, FarmWarDeployer undeploy my war both
from node1 and node2, but re-deploy it only on node1.
If I touch my war in my watchDir on node1, tomcat redeploys it correctly on
both nodes...
Is tomcat clustering used?
If so, does anybody us
Hi all,
I'm new to the list.
I'm trying to configure tomcat 6.0.33 clustering.
Session replication is ok.
I've a problem with FarmWarDeployer.
I found that:
1. You have to place the node under the element.
Tomcat 6.0.x complains that the element Cluster/Deployer element is not
understood at the
