geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gianny Damour <>
Subject Re: Question about deployment using farming plugin in G2.2
Date Wed, 26 Aug 2009 11:30:21 GMT
Hi Jeff,

You are correct. The name mangling has been reversed as it was  
causing pattern based GBean look-ups (e.g. finding DataSources) to fail.

To undeploy across the farm, users need to execute the undeploy  
command on the same node that they used to deploy/distribute their  
application across the farm. Note that this node acts as a kind of  
Administration Server, whereby it is the only node whose farming  
configuration needs to be maintained to reflect farm members and any  
lifecycle operations against farmed modules (e.g. start/stop) are  
propagated to the other nodes.


On 26/08/2009, at 4:28 PM, chi runhua wrote:

> Hi,
> In 
> deployment.html,  it says that a '_G_SLAVE' is appended to the  
> configuration name in ClusterStore.
> While using deploy/distribute in G2.2, a _G_MASTER is appended to  
> the configuration name in MasterConfigurationStore. And the target  
> application was deployed to ClusterStore with its pre-defined name  
> on the other nodes.
> To undeploy the application across a cluster, user should perform  
> deploy/undeploy command on the exact same node that he used to  
> deploy/distribute the application.
> Am I correct? if so, I will update the doc later.
> Thanks in advance.
> Jeff C

View raw message