Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 19178 invoked from network); 27 Aug 2009 02:13:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 27 Aug 2009 02:13:44 -0000 Received: (qmail 78242 invoked by uid 500); 27 Aug 2009 02:13:43 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 78163 invoked by uid 500); 27 Aug 2009 02:13:43 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 78155 invoked by uid 99); 27 Aug 2009 02:13:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Aug 2009 02:13:43 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of chirunhua@gmail.com designates 209.85.221.183 as permitted sender) Received: from [209.85.221.183] (HELO mail-qy0-f183.google.com) (209.85.221.183) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Aug 2009 02:13:35 +0000 Received: by qyk13 with SMTP id 13so368946qyk.3 for ; Wed, 26 Aug 2009 19:13:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=7O+teSv4oiDuvRiYzOo+3e7arhTmfQG3eLQ36R7AK3o=; b=l4IWCzWXa9E+gBT+oMRfExrvlDsOJUC2rXzGoU6ycBGn5VRhP06mBbJWb3NLwfLsFh LSn5mUHObwWGHSAL/K4PMR52hDKAbkoq9+QE/vUAU/5C8bY/0ETc1qsyJx5lckTw4iae jvUV3T/th80Pclo1kf+jTQM0Htnjddsw6zAiA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=LWqogG455atTXLMKr2oDuXv2toPrRe0g6L33o8WqWiTfHntgYXshMBEKaL8Eafplyb 1ea8esAYT6gGESYiHNrUSp/A8suF/z/Be93szItr7d29JYbo673umjwSm3RX0PGhJFYd bowiznamaIEJW3KFTQ+CnSThB+nVQ9z0NZz5k= MIME-Version: 1.0 Received: by 10.224.118.138 with SMTP id v10mr5936237qaq.13.1251339194179; Wed, 26 Aug 2009 19:13:14 -0700 (PDT) In-Reply-To: References: <98a659de0908252328j2cf5ffe6oefb79fd382310156@mail.gmail.com> Date: Thu, 27 Aug 2009 10:13:14 +0800 Message-ID: <98a659de0908261913i7f392b8aoae56b9a332ac6cfe@mail.gmail.com> Subject: Re: Question about deployment using farming plugin in G2.2 From: chi runhua To: user@geronimo.apache.org Content-Type: multipart/alternative; boundary=00c09f9b075a29a0b60472161ca1 X-Virus-Checked: Checked by ClamAV on apache.org --00c09f9b075a29a0b60472161ca1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Gianny, thanks alot. The page was updated accordingly. http://cwiki.apache.org/GMOxDOC22/farming-using-deployment.html Anything incorrect, please let me know. Jeff On Wed, Aug 26, 2009 at 7:30 PM, Gianny Damour < gianny.damour@optusnet.com.au> wrote: > 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. > > Thanks, > Gianny > > > On 26/08/2009, at 4:28 PM, chi runhua wrote: > > Hi, >> >> In http://cwiki.apache.org/GMOxDOC22/farming-using-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 >> >> >> >> >> > --00c09f9b075a29a0b60472161ca1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Gianny, thanks alot.

The page was updated accordingly.

http://cwiki.apache.org/GMOxDOC22/farming-using-deployment.htm= l

Anything incorrect, please let me know.

Jeff

On Wed, Aug 26, 2009 at 7:30 PM, Gianny Damour <gianny.damour= @optusnet.com.au> wrote:
Hi Jeff,

You are correct. The name mangling has been reversed as it was causing patt= ern 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, wher= eby 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.

Thanks,
Gianny


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

Hi,

In http://cwiki.apache.org/GMOxDOC22/farming-using-deployment.html,= =A0it 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 confi= guration name in MasterConfigurationStore. And the target application was d= eployed to ClusterStore with its pre-defined name on the other nodes.

To undeploy the application across a cluster, user should perform deploy/un= deploy 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






--00c09f9b075a29a0b60472161ca1--