Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 64324 invoked from network); 4 May 2006 15:30:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 May 2006 15:30:20 -0000 Received: (qmail 93983 invoked by uid 500); 4 May 2006 15:30:14 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 93946 invoked by uid 500); 4 May 2006 15:30:14 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 93935 invoked by uid 99); 4 May 2006 15:30:14 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 May 2006 08:30:14 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of rakesh.geronimo@gmail.com designates 64.233.162.200 as permitted sender) Received: from [64.233.162.200] (HELO nz-out-0102.google.com) (64.233.162.200) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 May 2006 08:30:13 -0700 Received: by nz-out-0102.google.com with SMTP id q3so495693nzb for ; Thu, 04 May 2006 08:29:52 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=Cy5wgHiTg1/4GNodgDUcQhI5doOQdN5TiuMd7evxrCGhADvXihAcC3Q/0uRaFdvyYCyZeVXr8HKNTQsPvvykOF6OldivU35akPgDRxIlKj7z9o9CUnB5tkypS9NAF8MtDC2/onD0c+oXLfwKFhnDlRHgKHfb7Qx+l2c+otDllPA= Received: by 10.65.233.9 with SMTP id k9mr388445qbr; Thu, 04 May 2006 08:29:52 -0700 (PDT) Received: by 10.65.230.7 with HTTP; Thu, 4 May 2006 08:29:52 -0700 (PDT) Message-ID: Date: Thu, 4 May 2006 20:59:52 +0530 From: "Rakesh Ranjan" To: dev@geronimo.apache.org Subject: Re: hot deployment directory In-Reply-To: <74e15baa0605040814l4e3e8ef6j2505afec4420d7e7@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_6284_197985.1146756592234" References: <74e15baa0605032149te19f66ehac7bc3f38c672163@mail.gmail.com> <74e15baa0605032211g61c781f7v81f442432d447e92@mail.gmail.com> <445A0077.1010802@earthlink.net> <74e15baa0605040814l4e3e8ef6j2505afec4420d7e7@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_6284_197985.1146756592234 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Aaron, Thanks for clarification. We will work without conflicting. I am going to touch the startup problem. = I mean if a module kept in hot deployment directory is already deployed, the server should not deploy the module again during the startup. Currently the server try to deploy the module again and throws exception. i already created a JIRA ID (GERONIMO-1982) for this. Rakesh Ranjan On 5/4/06, Aaron Mulder wrote: > > For purposes of the hot deployer functionality, forget that the SFHD > even exists. It is a special case feature, and does not at all > replace what the hot deploy directory does. > > However, for purposes of updatng the hot deployer implementation, you > may want to refer to the SFHD implementation. > > I'll probably be touching the hot deployer to add a feature so that if > an app is undeployed some other way the hot deployer will delete it > from its directory. Hopefully we can both work on this without > conflicting, since we'll be looking at different aspects of it. > > Thanks, > Aaron > > On 5/4/06, Rakesh Ranjan wrote: > > Thanks Joe. > > > > Still i have some confusions. > > > > Is SFHD the substitute for the DirectoryHotDeployer ? If it is > substitute, > > then do we need to disable the hotdeployment GBean for the working of > SFHD? > > What is the meaning of "It monitors just one directory for one > deployable > > element" ? > > > > Rakesh Ranjan > > > > > > > > > > > > On 5/4/06, Joe Bohn < joe.bohn@earthlink.net > wrote: > > > > > > SFHD is similar to hot deployer but has these differences: > > > > > > - It is not an integrated part of the server itself. It is a gbean > > > itself that must be deployed into the server to use it. > > > - It only takes action when the SFHD gbean is started (which is > > > typically during server startup). Hot Deploy monitors files for > > > changes at any time. > > > - It monitors just one directory for one deployable element > > > - It controls the life-cycle of the element it deploys. I'm not sur= e > > > if hot deploy does this as well. For example, a war deployed via thi= s > > > > mechanism is not added to the server config.xml for auto-start. > > > > > > You might want to consider my patches to SFHD as well included in > > > geronmio-1946 > > http://issues.apache.org/jira/browse/GERONIMO-1946 . > > > These haven't been blessed by Dain yet so they may change some. > > > > > > Joe > > > > > > > > > Rakesh Ranjan wrote: > > > > Can anybody please tell me the purpose of SingleFileHotDeploy > service. > > > > Is it same as the purpose of hot deployment directory? > > > > > > > > Rakesh Ranjan > > > > > > > > On 5/4/06, *Dain Sundstrom* < dain@iq80.com = > > > wrote: > > > > > > > > I suggest you start by reading the SingleFileHotDeploy service = I > > > > > wrote last week. It uses the most recent apis. > > > > > > > > -dain > > > > > > > > On May 3, 2006, at 10:30 PM, Rakesh Ranjan wrote: > > > > > > > > > I have seen the same problems with Geronimo-1.1-SNAPSHOTalso= . So > > i > > > > > will create JIRA ID for these two issues and start working. > > > > > Rakesh Ranjan > > > > > > > > > > On 5/4/06, Aaron Mulder > > > > wrote: > > > > > Please do any work in the 1.1 branch. Right now 1.2 is in a > very > > > > > uncertain state. Though, I suspect the issues will be > different > > in > > > > > 1.1, so you may want to start by testing the same things > there. > > > > > > > > > > IIRC, the hot deployer does not yet check the timestamp of > the > > > > > deployments in it its directory during startup and compare > those > > to > > > > > the timestamps of the current modules to determine whether a= n > > > > existing > > > > > file there is the same as ever or a new version was copied i= n > > while > > > > > the server was down. That should be doable in 1.1. > > > > > > > > > > Thanks, > > > > > Aaron > > > > > > > > > > On 5/4/06, Rakesh Ranjan < rakesh.geronimo@gmail.com > > > > > wrote: > > > > > > Thanks Aaron for the quick response. > > > > > > Here are two issues with Geronimo-1.2-SNAPSHOT which need > to > > be > > > > > fixed : > > > > > > 1. When Geronimo starts, it try to deploy the modules in > the > > hot > > > > > deployment > > > > > > directory even if that module is already deployed. Since > the > > > > > application is > > > > > > already deployed, it throws an error : the application > already > > > > > exists in the > > > > > > server. > > > > > > > > > > > > 2. Geronimo is not able to deploy the database plans kept > in > > the > > > > > hot > > > > > > deployment directory. > > > > > > > > > > > > Rakesh Ranjan > > > > > > > > > > > > > > > > > > On 5/4/06, Aaron Mulder < ammulder@alumni.princeton.edu > > > > > wrote: > > > > > > > You're welcome to look at that. Can you list the issues > > you're > > > > > going > > > > > > > to attempt to fix? There seems to be a lot of variation > in > > what > > > > > > > people think the problems actually are. > > > > > > > > > > > > > > Thanks, > > > > > > > Aaron > > > > > > > > > > > > > > On 5/4/06, Rakesh Ranjan < rakesh.geronimo@gmail.com > > > > > wrote: > > > > > > > > Hi all, > > > > > > > > > > > > > > > > I have not seen much activity in hot deployment > directory > > > > > enhancement. > > > > > > I > > > > > > > > have seen there are some bugs in the current > implementation > > > > > of hot > > > > > > > > deployment directory. I am interested to work on this > > > > > enhancement. So i > > > > > > want > > > > > > > > to know the current status of this enhancement? Is som= e > > other > > > > > member > > > > > > working > > > > > > > > on this issue? > > > > > > > > > > > > > > > > Rakesh > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Joe Bohn > > > joe.bohn at earthlink.net > > > > > > "He is no fool who gives what he cannot keep, to gain what he cannot > > > lose." -- Jim Elliot > > > > > > > > ------=_Part_6284_197985.1146756592234 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Aaron, Thanks for clarification.
We will work without conflicting. I am going to touch the startup problem. I mean if a module kept in hot deployment directory is already deployed, the server should not deploy the module again during the startup. Currently the server try to deploy the module again and throws exception. i already created a JIRA ID (GERONIMO-1982) for this.

Rakesh Ranjan

On 5/4/06, Aaron Mulder < ammulder@alumni.princeton.edu> wrote:
For purposes of the hot deployer functionality, forget that the SFHD
eve= n exists.  It is a special case feature, and does not at all
r= eplace what the hot deploy directory does.

However, for purposes of = updatng the hot deployer implementation, you
may want to refer to the SFHD implementation.

I'll probably be t= ouching the hot deployer to add a feature so that if
an app is undeploye= d some other way the hot deployer will delete it
from its directory.&nbs= p; Hopefully we can both work on this without
conflicting, since we'll be looking at different aspects of it.

= Thanks,
    Aaron

On 5/4/06, Rakesh Ranjan &l= t; rakesh.geronimo@gmail.com> wrote:
> Thanks Joe.
>
>  Still i have some confusions.
>
>&n= bsp; Is SFHD the substitute for the DirectoryHotDeployer ? If it is su= bstitute,
> then do we need to disable the hotdeployment GBean for th= e working of SFHD?
>  What is the meaning of "It monitors just one direc= tory for one deployable
> element" ?
>
>  = Rakesh Ranjan
>
>
>
>
>
> On 5/4/06, Jo= e Bohn < joe.bohn@earthlink.net > wrote:
> >
> > SFHD is si= milar to hot deployer but has these differences:
> >
> > = - It is not an integrated part of the server itself.   It is a gb= ean
> > itself that must be deployed into the server to use it.
> &= gt; - It only takes action when the SFHD gbean is started (which is
>= > typically during server startup).   Hot Deploy monitors fil= es for
> > changes at any time.
> > - It monitors just one dire= ctory for one deployable element
> > - It controls the life-cycle = of the element it deploys.   I'm not sure
> > if hot dep= loy does this as well.  For example, a war deployed via this
> > mechanism is not added to the server config.xml for auto-star= t.
> >
> > You might want to consider my patches to SFHD = as well included in
> > geronmio-1946
> http://issues.apache.org/jira/browse/GERONIMO-1946 .
> > These= haven't been blessed by Dain yet so they may change some.
> >
= > > Joe
> >
> >
> > Rakesh Ranjan wrote:
> > > Can anybody please tell me the purpose of SingleFileHotD= eploy service.
> > > Is it same as the purpose of hot deploymen= t directory?
> > >
> > > Rakesh Ranjan
> >= >
> > > On 5/4/06, *Dain Sundstrom* < dain@iq80.com <mailto: dain@iq80.com>>
> wrote:
> > >
> > >= ;     I suggest you start by reading the SingleFileHotD= eploy service I
> > >     wrote last week.  It u= ses the most recent apis.
> > >
> > >  &n= bsp;  -dain
> > >
> > >    = ; On May 3, 2006, at 10:30 PM, Rakesh Ranjan wrote:
> > >
> > >      > I have seen the = same problems with Geronimo-1.1-SNAPSHOT also. So
> i
> > &g= t;      > will create JIRA ID for these tw= o issues and start working.
> > >     =  > Rakesh Ranjan
> > >      >
> > >= ;      > On 5/4/06, Aaron Mulder <ammulder@alumni.princeton.edu
> > >     <mailto: ammulder@alumni.princeton.edu>> wrote:
> > >      > Please do any work in the 1.1 branch.  Right now 1.2 is in a very
> > >      > uncertain state.  Though, I suspect the issues will be different
> in=
> > >      > 1.1, so you may = want to start by testing the same things there.
> > > &nbs= p;    >
> > >    &nb= sp; > IIRC, the hot deployer does not yet check the timestamp of th= e
> > >      > deployments in i= t its directory during startup and compare those
> to
> > &g= t;      > the timestamps of the current mo= dules to determine whether an
> > >     exi= sting
> > >      > file there is th= e same as ever or a new version was copied in
> while
> > &g= t;      > the server was down.  = That should be doable in 1.1.
> > >    &nbs= p; >
> > >      > Than= ks,
> > >      >   = ;  Aaron
> > >      >
= > > >      > On 5/4/06, Rakesh Ra= njan < rakesh.geronimo@gmail.com
> > >     <= ;mailto:=20 rakesh.geronimo@gmail.com&= gt;> wrote:
> > >      > &g= t; Thanks Aaron for the quick response.
> > >      > >  Here are two issues with Geronimo-1.2-SNAPSHOT which need to
> be
> = > >      > fixed :
> > >      > >  1. When Geronimo starts, it try to deploy the modules in the
> hot
&g= t; > >      > deployment
> >= ; >      > > directory even if that = module is already deployed. Since the
> > >   &n= bsp;  > application is
> > >      > > already dep= loyed, it throws an error : the application already
> > > =      > exists in the
> > > &nb= sp;    > > server.
> > >  &= nbsp;   > >
> > >      > >  2. Geronimo is not able to deploy the database plans kept in
> the
&g= t; > >      > hot
> > >&= nbsp;     > > deployment directory.
> = > >      > >
> > >&nb= sp;     > >  Rakesh Ranjan
> > >      > >
> >= ; >      > >
> > > =      > > On 5/4/06, Aaron Mulder < ammulder@alumni.princeton.edu
> > >    = <mailto:=20 ammulder@alumni.princeton= .edu>> wrote:
> > >      > > > You're welcome to look at that.  Can you list the issues
> you're<= br>> > >      > going
> > >      > > > to attempt to fix?  There seems to be a lot of variation in
> what
= > > >      > > > people thi= nk the problems actually are.
> > >    &nbs= p; > > >
> > >      = ;> > > Thanks,
> > >      > > > &= nbsp;   Aaron
> > >     &nbs= p;> > >
> > >      > = > > On 5/4/06, Rakesh Ranjan < rakesh.geronimo@gmail.com
> > >     <mailto: rakesh.geronimo@gmail.com>> wrote:> > >      > > > > Hi = all,
> > >      > > > > > > >      > > > >  I have not seen much activity in hot deployment directory
> > >      > enhance= ment.
> > >      > > I
&= gt; > >      > > > > have seen there are some bugs in the current implementation
> > >&nb= sp;     > of hot
> > >  &= nbsp;   > > > > deployment directory. I am inter= ested to work on this
> > >      = > enhancement. So i
> > >      > > want
>= ; > >      > > > > to know = the current status of this enhancement? Is some
> other
> > = >      > member
> > > =      > > working
> > >      > > > > o= n this issue?
> > >      > >= ; > >
> > >      > > = > >  Rakesh
> > >     =  > > > >
> > >     &n= bsp;> > >
> > >      > >
> >= ; >      > >
> > > =      >
> > >
> > >
&= gt; >
> > --
> > Joe Bohn
> > joe.bohn at earthlink.net
> >
> > "He is no fool who gives w= hat he cannot keep, to gain what he cannot
> > lose." &n= bsp; -- Jim Elliot
> >
>
>

------=_Part_6284_197985.1146756592234--