You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by lak n <ma...@gmail.com> on 2006/04/05 11:34:10 UTC
When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory.
Hot deployment Issue :
When already an application module say (hello.war) is deployed (either
by using manually or hot deploy procedure ) , And when some one try to *hot
deploy the same application *with same or different name ( say hello.war |
hello2.war | hello2 directory ) , the server throws an exception saying
there exists already an application deployed , But doesn't delete the module
( hello.war | hello2.war | hello2 directory) from hot deploy directory
thus the next time the server starts , it tries to deploy the same module
once again.
I think the better option in this case would be to delete the
unsuccessfully hot deployed application file or directory from hot deploy
directory and show some message.
With Thanks and Regards,
Mansoor
Re: When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory.
Posted by Dain Sundstrom <da...@iq80.com>.
I agree that we need to make sure we only have the app in one of the
three directories.
BTW does anyone know how tomcat handles this? IIRC they have a
console that you can use to manage the life cycle of applications.
-dain
On Apr 5, 2006, at 11:31 AM, Aaron Mulder wrote:
> That's a cool idea, but we have to make sure to delete the entry in
> the stopped dir if you deploy successfully later. And we still have
> to delete the entry in whatever place if you subsequently un/re/deploy
> through the deploy tool or console, etc.
>
> Aaron
>
> On 4/5/06, Dain Sundstrom <da...@iq80.com> wrote:
>> I been thinking that we could have sub-directories under deploy that
>> we move the deployment to when it is stopped or has a deployment
>> failure. We could also write a note to the faild dir with a reason
>> for it being in that dir. I'm thinking of something like this:
>>
>> Starting/Running:
>> deploy/foo.war
>>
>> Stopped:
>> deploy/stopped/foo.war
>>
>> Failed:
>> deploy/stopped/foo.war
>> deploy/stopped/foo.war.txt
>>
>> What do you think?
>>
>> -dain
>>
>> On Apr 5, 2006, at 7:01 AM, Aaron Mulder wrote:
>>
>>> Sure, you can create a JIRA and post a patch.
>>>
>>> Thanks,
>>> Aaron
>>>
>>> On 4/5/06, Mansoor <ma...@gmail.com> wrote:
>>>>
>>>> Thanks Aaron for your prompt response ,
>>>>
>>>> I was thinking , whether we can put this feature into our geronimo.
>>>> Infact i have written a piece of code , that removes this
>>>> problem.should i
>>>> need to raise a jira and submit as a patch ?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 4/5/06, Aaron Mulder <am...@alumni.princeton.edu> wrote:
>>>>> OK. For now, we recommend that you only use one deployment
>>>>> method on
>>>>> any given application -- always use the hot deploy dir, or always
>>>>> use
>>>>> the command-line deploy tool, etc. It's definitely possible to
>>>>> confuse things at the moment by switching techniques for the same
>>>>> application or module.
>>>>>
>>>>> Thanks,
>>>>> Aaron
>>>>>
>>>>> On 4/5/06, lak n < man.geronimo@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>> Hot deployment Issue :
>>>>>> When already an application module say (hello.war) is
>>>>>> deployed
>>>> (either
>>>>>> by using manually or hot deploy procedure ) , And when some one
>>>>>> try to
>>>> hot
>>>>>> deploy the same application with same or different name ( say
>>>>>> hello.war
>>>> |
>>>>>> hello2.war | hello2 directory ) , the server throws an
>>>>>> exception saying
>>>>>> there exists already an application deployed , But doesn't
>>>>>> delete the
>>>> module
>>>>>> ( hello.war | hello2.war | hello2 directory) from hot deploy
>>>>>> directory
>>>>>> thus the next time the server starts , it tries to deploy the
>>>>>> same
>>>> module
>>>>>> once again.
>>>>>>
>>>>>> I think the better option in this case would be to delete the
>>>>>> unsuccessfully hot deployed application file or directory from
>>>>>> hot
>>>> deploy
>>>>>> directory and show some message.
>>>>>>
>>>>>> With Thanks and Regards,
>>>>>> Mansoor
>>>>>
>>>>
>>>>
>>
>>
Re: When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory.
Posted by Bruce Snyder <br...@gmail.com>.
On 4/5/06, Dain Sundstrom <da...@iq80.com> wrote:
> On Apr 5, 2006, at 12:20 PM, Sachin Patel wrote:
>
> > So it looks like we need to re-evaluate the future intent of hot-
> > deploy. Should it remain a "drop, pray & test" method of
> > deployment for development scenarios or should it be consider a
> > full-fledged primary method of deploying final version of apps?.
>
> I think some users will use it as their main method of deployment, so
> we should try to make is as reliable as possible.
Agreed.
> > On Apr 5, 2006, at 3:09 PM, Bruce Snyder wrote:
> >
> >> This is certainly an interesting idea and maybe a step toward
> >> versioning of apps that are deployed in Geronimo. I like this idea a
> >> lot, but I'm curious to discuss this in more detail. Based on the
> >> proposed status above, how will this work when there are many copies
> >> of a given app? Will the deployer subsystem need to rake all of these
> >> files and then determine the version to actually deploy? I think we
> >> need a richer model than that, especially when considering
> >> clustering.
>
> Now I'm confused. I thought this was just a dump of the current
> status of deployed applications in the server. I wouldn't expect the
> server to read this file, but I can see shell scripts reading it.
Sorry, I wasn't trying to confuse things. I'm trying to take the
discussion a step further to consider versioning of apps deployed in
Geronimo.
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache Geronimo (http://geronimo.apache.org/)
Castor (http://castor.org/)
Re: When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory.
Posted by Jason Dillon <ja...@planet57.com>.
> Now I'm confused. I thought this was just a dump of the current
> status of deployed applications in the server. I wouldn't expect
> the server to read this file, but I can see shell scripts reading it.
It might make more sense to provide a cmd line tool to dump this
information, rather than have the server spit it out. If this is
really for admin and scripts, then it might be nicer to allow more
control over how the information gets spit up... which flags to a cmd
could easily provide.
--jason
Re: When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory.
Posted by Dain Sundstrom <da...@iq80.com>.
On Apr 5, 2006, at 12:20 PM, Sachin Patel wrote:
> So it looks like we need to re-evaluate the future intent of hot-
> deploy. Should it remain a "drop, pray & test" method of
> deployment for development scenarios or should it be consider a
> full-fledged primary method of deploying final version of apps?.
I think some users will use it as their main method of deployment, so
we should try to make is as reliable as possible.
> On Apr 5, 2006, at 3:09 PM, Bruce Snyder wrote:
>
>> This is certainly an interesting idea and maybe a step toward
>> versioning of apps that are deployed in Geronimo. I like this idea a
>> lot, but I'm curious to discuss this in more detail. Based on the
>> proposed status above, how will this work when there are many copies
>> of a given app? Will the deployer subsystem need to rake all of these
>> files and then determine the version to actually deploy? I think we
>> need a richer model than that, especially when considering
>> clustering.
Now I'm confused. I thought this was just a dump of the current
status of deployed applications in the server. I wouldn't expect the
server to read this file, but I can see shell scripts reading it.
-dain
Re: When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory.
Posted by Sachin Patel <sp...@gmail.com>.
So it looks like we need to re-evaluate the future intent of hot-
deploy. Should it remain a "drop, pray & test" method of deployment
for development scenarios or should it be consider a full-fledged
primary method of deploying final version of apps?.
- sachin
On Apr 5, 2006, at 3:09 PM, Bruce Snyder wrote:
> On 4/5/06, Sachin Patel <sp...@gmail.com> wrote:
>> Could we just provide a single status file for all archives with info
>> like... This way rather then a user having to traverse directories
>> all the info is available in the single file.
>>
>> ARCHIVE, LAST PUBLISH TIME, LAST PUBLISH STATE, LAST PUBLISH MESSAGE
>
> This is certainly an interesting idea and maybe a step toward
> versioning of apps that are deployed in Geronimo. I like this idea a
> lot, but I'm curious to discuss this in more detail. Based on the
> proposed status above, how will this work when there are many copies
> of a given app? Will the deployer subsystem need to rake all of these
> files and then determine the version to actually deploy? I think we
> need a richer model than that, especially when considering clustering.
>
> Bruce
> --
> perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!
> G;6%I;\"YC;VT*"
> );'
>
> Apache Geronimo (http://geronimo.apache.org/)
>
> Castor (http://castor.org/)
Re: When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory.
Posted by Bruce Snyder <br...@gmail.com>.
On 4/5/06, Bruce Snyder <br...@gmail.com> wrote:
> On 4/5/06, Sachin Patel <sp...@gmail.com> wrote:
> > Could we just provide a single status file for all archives with info
> > like... This way rather then a user having to traverse directories
> > all the info is available in the single file.
> >
> > ARCHIVE, LAST PUBLISH TIME, LAST PUBLISH STATE, LAST PUBLISH MESSAGE
>
> This is certainly an interesting idea and maybe a step toward
> versioning of apps that are deployed in Geronimo. I like this idea a
> lot, but I'm curious to discuss this in more detail. Based on the
> proposed status above, how will this work when there are many copies
> of a given app? Will the deployer subsystem need to rake all of these
> files and then determine the version to actually deploy? I think we
> need a richer model than that, especially when considering clustering.
Actually, isn't a Maven repo embedded in 1.1? We could probably make
use of this for versioning apps.
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache Geronimo (http://geronimo.apache.org/)
Castor (http://castor.org/)
Re: When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory.
Posted by Bruce Snyder <br...@gmail.com>.
On 4/5/06, Sachin Patel <sp...@gmail.com> wrote:
> Could we just provide a single status file for all archives with info
> like... This way rather then a user having to traverse directories
> all the info is available in the single file.
>
> ARCHIVE, LAST PUBLISH TIME, LAST PUBLISH STATE, LAST PUBLISH MESSAGE
This is certainly an interesting idea and maybe a step toward
versioning of apps that are deployed in Geronimo. I like this idea a
lot, but I'm curious to discuss this in more detail. Based on the
proposed status above, how will this work when there are many copies
of a given app? Will the deployer subsystem need to rake all of these
files and then determine the version to actually deploy? I think we
need a richer model than that, especially when considering clustering.
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache Geronimo (http://geronimo.apache.org/)
Castor (http://castor.org/)
Re: When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory.
Posted by Jason Dillon <ja...@planet57.com>.
Why not use an XML file for the status?
--jason
On Apr 5, 2006, at 11:52 AM, Dain Sundstrom wrote:
> Interesting idea. The only question I have is how do we allow for
> messages that contain stack traces using this file format?
>
> -dain
>
> On Apr 5, 2006, at 11:37 AM, Sachin Patel wrote:
>
>> Could we just provide a single status file for all archives with
>> info like... This way rather then a user having to traverse
>> directories all the info is available in the single file.
>>
>> ARCHIVE, LAST PUBLISH TIME, LAST PUBLISH STATE, LAST PUBLISH MESSAGE
>>
>> - sachin
>>
>>
>>
>> On Apr 5, 2006, at 2:31 PM, Aaron Mulder wrote:
>>
>>> That's a cool idea, but we have to make sure to delete the entry in
>>> the stopped dir if you deploy successfully later. And we still have
>>> to delete the entry in whatever place if you subsequently un/re/
>>> deploy
>>> through the deploy tool or console, etc.
>>>
>>> Aaron
>>>
>>> On 4/5/06, Dain Sundstrom <da...@iq80.com> wrote:
>>>> I been thinking that we could have sub-directories under deploy
>>>> that
>>>> we move the deployment to when it is stopped or has a deployment
>>>> failure. We could also write a note to the faild dir with a reason
>>>> for it being in that dir. I'm thinking of something like this:
>>>>
>>>> Starting/Running:
>>>> deploy/foo.war
>>>>
>>>> Stopped:
>>>> deploy/stopped/foo.war
>>>>
>>>> Failed:
>>>> deploy/stopped/foo.war
>>>> deploy/stopped/foo.war.txt
>>>>
>>>> What do you think?
>>>>
>>>> -dain
>>>>
>>>> On Apr 5, 2006, at 7:01 AM, Aaron Mulder wrote:
>>>>
>>>>> Sure, you can create a JIRA and post a patch.
>>>>>
>>>>> Thanks,
>>>>> Aaron
>>>>>
>>>>> On 4/5/06, Mansoor <ma...@gmail.com> wrote:
>>>>>>
>>>>>> Thanks Aaron for your prompt response ,
>>>>>>
>>>>>> I was thinking , whether we can put this feature into our
>>>>>> geronimo.
>>>>>> Infact i have written a piece of code , that removes this
>>>>>> problem.should i
>>>>>> need to raise a jira and submit as a patch ?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 4/5/06, Aaron Mulder <am...@alumni.princeton.edu> wrote:
>>>>>>> OK. For now, we recommend that you only use one deployment
>>>>>>> method on
>>>>>>> any given application -- always use the hot deploy dir, or
>>>>>>> always
>>>>>>> use
>>>>>>> the command-line deploy tool, etc. It's definitely possible to
>>>>>>> confuse things at the moment by switching techniques for the
>>>>>>> same
>>>>>>> application or module.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Aaron
>>>>>>>
>>>>>>> On 4/5/06, lak n < man.geronimo@gmail.com> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> Hot deployment Issue :
>>>>>>>> When already an application module say (hello.war) is
>>>>>>>> deployed
>>>>>> (either
>>>>>>>> by using manually or hot deploy procedure ) , And when some one
>>>>>>>> try to
>>>>>> hot
>>>>>>>> deploy the same application with same or different name ( say
>>>>>>>> hello.war
>>>>>> |
>>>>>>>> hello2.war | hello2 directory ) , the server throws an
>>>>>>>> exception saying
>>>>>>>> there exists already an application deployed , But doesn't
>>>>>>>> delete the
>>>>>> module
>>>>>>>> ( hello.war | hello2.war | hello2 directory) from hot deploy
>>>>>>>> directory
>>>>>>>> thus the next time the server starts , it tries to deploy
>>>>>>>> the same
>>>>>> module
>>>>>>>> once again.
>>>>>>>>
>>>>>>>> I think the better option in this case would be to delete
>>>>>>>> the
>>>>>>>> unsuccessfully hot deployed application file or directory
>>>>>>>> from hot
>>>>>> deploy
>>>>>>>> directory and show some message.
>>>>>>>>
>>>>>>>> With Thanks and Regards,
>>>>>>>> Mansoor
>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>
Re: When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory.
Posted by Dain Sundstrom <da...@iq80.com>.
Interesting idea. The only question I have is how do we allow for
messages that contain stack traces using this file format?
-dain
On Apr 5, 2006, at 11:37 AM, Sachin Patel wrote:
> Could we just provide a single status file for all archives with
> info like... This way rather then a user having to traverse
> directories all the info is available in the single file.
>
> ARCHIVE, LAST PUBLISH TIME, LAST PUBLISH STATE, LAST PUBLISH MESSAGE
>
> - sachin
>
>
>
> On Apr 5, 2006, at 2:31 PM, Aaron Mulder wrote:
>
>> That's a cool idea, but we have to make sure to delete the entry in
>> the stopped dir if you deploy successfully later. And we still have
>> to delete the entry in whatever place if you subsequently un/re/
>> deploy
>> through the deploy tool or console, etc.
>>
>> Aaron
>>
>> On 4/5/06, Dain Sundstrom <da...@iq80.com> wrote:
>>> I been thinking that we could have sub-directories under deploy that
>>> we move the deployment to when it is stopped or has a deployment
>>> failure. We could also write a note to the faild dir with a reason
>>> for it being in that dir. I'm thinking of something like this:
>>>
>>> Starting/Running:
>>> deploy/foo.war
>>>
>>> Stopped:
>>> deploy/stopped/foo.war
>>>
>>> Failed:
>>> deploy/stopped/foo.war
>>> deploy/stopped/foo.war.txt
>>>
>>> What do you think?
>>>
>>> -dain
>>>
>>> On Apr 5, 2006, at 7:01 AM, Aaron Mulder wrote:
>>>
>>>> Sure, you can create a JIRA and post a patch.
>>>>
>>>> Thanks,
>>>> Aaron
>>>>
>>>> On 4/5/06, Mansoor <ma...@gmail.com> wrote:
>>>>>
>>>>> Thanks Aaron for your prompt response ,
>>>>>
>>>>> I was thinking , whether we can put this feature into our
>>>>> geronimo.
>>>>> Infact i have written a piece of code , that removes this
>>>>> problem.should i
>>>>> need to raise a jira and submit as a patch ?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 4/5/06, Aaron Mulder <am...@alumni.princeton.edu> wrote:
>>>>>> OK. For now, we recommend that you only use one deployment
>>>>>> method on
>>>>>> any given application -- always use the hot deploy dir, or always
>>>>>> use
>>>>>> the command-line deploy tool, etc. It's definitely possible to
>>>>>> confuse things at the moment by switching techniques for the same
>>>>>> application or module.
>>>>>>
>>>>>> Thanks,
>>>>>> Aaron
>>>>>>
>>>>>> On 4/5/06, lak n < man.geronimo@gmail.com> wrote:
>>>>>>>
>>>>>>>
>>>>>>> Hot deployment Issue :
>>>>>>> When already an application module say (hello.war) is
>>>>>>> deployed
>>>>> (either
>>>>>>> by using manually or hot deploy procedure ) , And when some one
>>>>>>> try to
>>>>> hot
>>>>>>> deploy the same application with same or different name ( say
>>>>>>> hello.war
>>>>> |
>>>>>>> hello2.war | hello2 directory ) , the server throws an
>>>>>>> exception saying
>>>>>>> there exists already an application deployed , But doesn't
>>>>>>> delete the
>>>>> module
>>>>>>> ( hello.war | hello2.war | hello2 directory) from hot deploy
>>>>>>> directory
>>>>>>> thus the next time the server starts , it tries to deploy the
>>>>>>> same
>>>>> module
>>>>>>> once again.
>>>>>>>
>>>>>>> I think the better option in this case would be to delete the
>>>>>>> unsuccessfully hot deployed application file or directory
>>>>>>> from hot
>>>>> deploy
>>>>>>> directory and show some message.
>>>>>>>
>>>>>>> With Thanks and Regards,
>>>>>>> Mansoor
>>>>>>
>>>>>
>>>>>
>>>
>>>
Re: When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory.
Posted by Sachin Patel <sp...@gmail.com>.
Could we just provide a single status file for all archives with info
like... This way rather then a user having to traverse directories
all the info is available in the single file.
ARCHIVE, LAST PUBLISH TIME, LAST PUBLISH STATE, LAST PUBLISH MESSAGE
- sachin
On Apr 5, 2006, at 2:31 PM, Aaron Mulder wrote:
> That's a cool idea, but we have to make sure to delete the entry in
> the stopped dir if you deploy successfully later. And we still have
> to delete the entry in whatever place if you subsequently un/re/deploy
> through the deploy tool or console, etc.
>
> Aaron
>
> On 4/5/06, Dain Sundstrom <da...@iq80.com> wrote:
>> I been thinking that we could have sub-directories under deploy that
>> we move the deployment to when it is stopped or has a deployment
>> failure. We could also write a note to the faild dir with a reason
>> for it being in that dir. I'm thinking of something like this:
>>
>> Starting/Running:
>> deploy/foo.war
>>
>> Stopped:
>> deploy/stopped/foo.war
>>
>> Failed:
>> deploy/stopped/foo.war
>> deploy/stopped/foo.war.txt
>>
>> What do you think?
>>
>> -dain
>>
>> On Apr 5, 2006, at 7:01 AM, Aaron Mulder wrote:
>>
>>> Sure, you can create a JIRA and post a patch.
>>>
>>> Thanks,
>>> Aaron
>>>
>>> On 4/5/06, Mansoor <ma...@gmail.com> wrote:
>>>>
>>>> Thanks Aaron for your prompt response ,
>>>>
>>>> I was thinking , whether we can put this feature into our geronimo.
>>>> Infact i have written a piece of code , that removes this
>>>> problem.should i
>>>> need to raise a jira and submit as a patch ?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 4/5/06, Aaron Mulder <am...@alumni.princeton.edu> wrote:
>>>>> OK. For now, we recommend that you only use one deployment
>>>>> method on
>>>>> any given application -- always use the hot deploy dir, or always
>>>>> use
>>>>> the command-line deploy tool, etc. It's definitely possible to
>>>>> confuse things at the moment by switching techniques for the same
>>>>> application or module.
>>>>>
>>>>> Thanks,
>>>>> Aaron
>>>>>
>>>>> On 4/5/06, lak n < man.geronimo@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>> Hot deployment Issue :
>>>>>> When already an application module say (hello.war) is
>>>>>> deployed
>>>> (either
>>>>>> by using manually or hot deploy procedure ) , And when some one
>>>>>> try to
>>>> hot
>>>>>> deploy the same application with same or different name ( say
>>>>>> hello.war
>>>> |
>>>>>> hello2.war | hello2 directory ) , the server throws an
>>>>>> exception saying
>>>>>> there exists already an application deployed , But doesn't
>>>>>> delete the
>>>> module
>>>>>> ( hello.war | hello2.war | hello2 directory) from hot deploy
>>>>>> directory
>>>>>> thus the next time the server starts , it tries to deploy the
>>>>>> same
>>>> module
>>>>>> once again.
>>>>>>
>>>>>> I think the better option in this case would be to delete the
>>>>>> unsuccessfully hot deployed application file or directory from
>>>>>> hot
>>>> deploy
>>>>>> directory and show some message.
>>>>>>
>>>>>> With Thanks and Regards,
>>>>>> Mansoor
>>>>>
>>>>
>>>>
>>
>>
Re: When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory.
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
That's a cool idea, but we have to make sure to delete the entry in
the stopped dir if you deploy successfully later. And we still have
to delete the entry in whatever place if you subsequently un/re/deploy
through the deploy tool or console, etc.
Aaron
On 4/5/06, Dain Sundstrom <da...@iq80.com> wrote:
> I been thinking that we could have sub-directories under deploy that
> we move the deployment to when it is stopped or has a deployment
> failure. We could also write a note to the faild dir with a reason
> for it being in that dir. I'm thinking of something like this:
>
> Starting/Running:
> deploy/foo.war
>
> Stopped:
> deploy/stopped/foo.war
>
> Failed:
> deploy/stopped/foo.war
> deploy/stopped/foo.war.txt
>
> What do you think?
>
> -dain
>
> On Apr 5, 2006, at 7:01 AM, Aaron Mulder wrote:
>
> > Sure, you can create a JIRA and post a patch.
> >
> > Thanks,
> > Aaron
> >
> > On 4/5/06, Mansoor <ma...@gmail.com> wrote:
> >>
> >> Thanks Aaron for your prompt response ,
> >>
> >> I was thinking , whether we can put this feature into our geronimo.
> >> Infact i have written a piece of code , that removes this
> >> problem.should i
> >> need to raise a jira and submit as a patch ?
> >>
> >>
> >>
> >>
> >>
> >> On 4/5/06, Aaron Mulder <am...@alumni.princeton.edu> wrote:
> >>> OK. For now, we recommend that you only use one deployment
> >>> method on
> >>> any given application -- always use the hot deploy dir, or always
> >>> use
> >>> the command-line deploy tool, etc. It's definitely possible to
> >>> confuse things at the moment by switching techniques for the same
> >>> application or module.
> >>>
> >>> Thanks,
> >>> Aaron
> >>>
> >>> On 4/5/06, lak n < man.geronimo@gmail.com> wrote:
> >>>>
> >>>>
> >>>> Hot deployment Issue :
> >>>> When already an application module say (hello.war) is deployed
> >> (either
> >>>> by using manually or hot deploy procedure ) , And when some one
> >>>> try to
> >> hot
> >>>> deploy the same application with same or different name ( say
> >>>> hello.war
> >> |
> >>>> hello2.war | hello2 directory ) , the server throws an
> >>>> exception saying
> >>>> there exists already an application deployed , But doesn't
> >>>> delete the
> >> module
> >>>> ( hello.war | hello2.war | hello2 directory) from hot deploy
> >>>> directory
> >>>> thus the next time the server starts , it tries to deploy the same
> >> module
> >>>> once again.
> >>>>
> >>>> I think the better option in this case would be to delete the
> >>>> unsuccessfully hot deployed application file or directory from hot
> >> deploy
> >>>> directory and show some message.
> >>>>
> >>>> With Thanks and Regards,
> >>>> Mansoor
> >>>
> >>
> >>
>
>
Re: When already deployed application is hot deployed once gain ,
Server doesn't delete the module from hot deployed directory.
Posted by Matt Hogstrom <ma...@hogstrom.org>.
I like the idea of conveying information alot. Although, as a developer I think I'd like to look in
one place for the app and its status. We could prefix or annotate the messages in the log so an
association of messages and stack traces could be made to the application.
For Bruces comment on versioning, if the apps are CARS then they would get a version number anyway
and would all fit basically in the same place.
Dain Sundstrom wrote:
> I been thinking that we could have sub-directories under deploy that we
> move the deployment to when it is stopped or has a deployment failure.
> We could also write a note to the faild dir with a reason for it being
> in that dir. I'm thinking of something like this:
>
> Starting/Running:
> deploy/foo.war
>
> Stopped:
> deploy/stopped/foo.war
>
> Failed:
> deploy/stopped/foo.war
> deploy/stopped/foo.war.txt
>
> What do you think?
>
> -dain
>
> On Apr 5, 2006, at 7:01 AM, Aaron Mulder wrote:
>
>> Sure, you can create a JIRA and post a patch.
>>
>> Thanks,
>> Aaron
>>
>> On 4/5/06, Mansoor <ma...@gmail.com> wrote:
>>
>>>
>>> Thanks Aaron for your prompt response ,
>>>
>>> I was thinking , whether we can put this feature into our geronimo.
>>> Infact i have written a piece of code , that removes this
>>> problem.should i
>>> need to raise a jira and submit as a patch ?
>>>
>>>
>>>
>>>
>>>
>>> On 4/5/06, Aaron Mulder <am...@alumni.princeton.edu> wrote:
>>>
>>>> OK. For now, we recommend that you only use one deployment method on
>>>> any given application -- always use the hot deploy dir, or always use
>>>> the command-line deploy tool, etc. It's definitely possible to
>>>> confuse things at the moment by switching techniques for the same
>>>> application or module.
>>>>
>>>> Thanks,
>>>> Aaron
>>>>
>>>> On 4/5/06, lak n < man.geronimo@gmail.com> wrote:
>>>>
>>>>>
>>>>>
>>>>> Hot deployment Issue :
>>>>> When already an application module say (hello.war) is deployed
>>>
>>> (either
>>>
>>>>> by using manually or hot deploy procedure ) , And when some one
>>>>> try to
>>>
>>> hot
>>>
>>>>> deploy the same application with same or different name ( say
>>>>> hello.war
>>>
>>> |
>>>
>>>>> hello2.war | hello2 directory ) , the server throws an exception
>>>>> saying
>>>>> there exists already an application deployed , But doesn't delete the
>>>
>>> module
>>>
>>>>> ( hello.war | hello2.war | hello2 directory) from hot deploy
>>>>> directory
>>>>> thus the next time the server starts , it tries to deploy the same
>>>
>>> module
>>>
>>>>> once again.
>>>>>
>>>>> I think the better option in this case would be to delete the
>>>>> unsuccessfully hot deployed application file or directory from hot
>>>
>>> deploy
>>>
>>>>> directory and show some message.
>>>>>
>>>>> With Thanks and Regards,
>>>>> Mansoor
>>>>
>>>>
>>>
>>>
>
>
>
>
Re: When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory.
Posted by Dain Sundstrom <da...@iq80.com>.
I been thinking that we could have sub-directories under deploy that
we move the deployment to when it is stopped or has a deployment
failure. We could also write a note to the faild dir with a reason
for it being in that dir. I'm thinking of something like this:
Starting/Running:
deploy/foo.war
Stopped:
deploy/stopped/foo.war
Failed:
deploy/stopped/foo.war
deploy/stopped/foo.war.txt
What do you think?
-dain
On Apr 5, 2006, at 7:01 AM, Aaron Mulder wrote:
> Sure, you can create a JIRA and post a patch.
>
> Thanks,
> Aaron
>
> On 4/5/06, Mansoor <ma...@gmail.com> wrote:
>>
>> Thanks Aaron for your prompt response ,
>>
>> I was thinking , whether we can put this feature into our geronimo.
>> Infact i have written a piece of code , that removes this
>> problem.should i
>> need to raise a jira and submit as a patch ?
>>
>>
>>
>>
>>
>> On 4/5/06, Aaron Mulder <am...@alumni.princeton.edu> wrote:
>>> OK. For now, we recommend that you only use one deployment
>>> method on
>>> any given application -- always use the hot deploy dir, or always
>>> use
>>> the command-line deploy tool, etc. It's definitely possible to
>>> confuse things at the moment by switching techniques for the same
>>> application or module.
>>>
>>> Thanks,
>>> Aaron
>>>
>>> On 4/5/06, lak n < man.geronimo@gmail.com> wrote:
>>>>
>>>>
>>>> Hot deployment Issue :
>>>> When already an application module say (hello.war) is deployed
>> (either
>>>> by using manually or hot deploy procedure ) , And when some one
>>>> try to
>> hot
>>>> deploy the same application with same or different name ( say
>>>> hello.war
>> |
>>>> hello2.war | hello2 directory ) , the server throws an
>>>> exception saying
>>>> there exists already an application deployed , But doesn't
>>>> delete the
>> module
>>>> ( hello.war | hello2.war | hello2 directory) from hot deploy
>>>> directory
>>>> thus the next time the server starts , it tries to deploy the same
>> module
>>>> once again.
>>>>
>>>> I think the better option in this case would be to delete the
>>>> unsuccessfully hot deployed application file or directory from hot
>> deploy
>>>> directory and show some message.
>>>>
>>>> With Thanks and Regards,
>>>> Mansoor
>>>
>>
>>
Re: When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory.
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
Sure, you can create a JIRA and post a patch.
Thanks,
Aaron
On 4/5/06, Mansoor <ma...@gmail.com> wrote:
>
> Thanks Aaron for your prompt response ,
>
> I was thinking , whether we can put this feature into our geronimo.
> Infact i have written a piece of code , that removes this problem.should i
> need to raise a jira and submit as a patch ?
>
>
>
>
>
> On 4/5/06, Aaron Mulder <am...@alumni.princeton.edu> wrote:
> > OK. For now, we recommend that you only use one deployment method on
> > any given application -- always use the hot deploy dir, or always use
> > the command-line deploy tool, etc. It's definitely possible to
> > confuse things at the moment by switching techniques for the same
> > application or module.
> >
> > Thanks,
> > Aaron
> >
> > On 4/5/06, lak n < man.geronimo@gmail.com> wrote:
> > >
> > >
> > > Hot deployment Issue :
> > > When already an application module say (hello.war) is deployed
> (either
> > > by using manually or hot deploy procedure ) , And when some one try to
> hot
> > > deploy the same application with same or different name ( say hello.war
> |
> > > hello2.war | hello2 directory ) , the server throws an exception saying
> > > there exists already an application deployed , But doesn't delete the
> module
> > > ( hello.war | hello2.war | hello2 directory) from hot deploy directory
> > > thus the next time the server starts , it tries to deploy the same
> module
> > > once again.
> > >
> > > I think the better option in this case would be to delete the
> > > unsuccessfully hot deployed application file or directory from hot
> deploy
> > > directory and show some message.
> > >
> > > With Thanks and Regards,
> > > Mansoor
> >
>
>
Re: When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory.
Posted by Mansoor <ma...@gmail.com>.
>
> Thanks Aaron for your prompt response ,
>
> I was thinking , whether we can put this feature into our geronimo.
> Infact i have written a piece of code , that removes this problem.should i
> need to raise a jira and submit as a patch ?
>
>
>
>
> On 4/5/06, Aaron Mulder <am...@alumni.princeton.edu> wrote:
> >
> > OK. For now, we recommend that you only use one deployment method on
> > any given application -- always use the hot deploy dir, or always use
> > the command-line deploy tool, etc. It's definitely possible to
> > confuse things at the moment by switching techniques for the same
> > application or module.
> >
> > Thanks,
> > Aaron
> >
> > On 4/5/06, lak n < man.geronimo@gmail.com> wrote:
> > >
> > >
> > > Hot deployment Issue :
> > > When already an application module say (hello.war) is deployed
> > (either
> > > by using manually or hot deploy procedure ) , And when some one try to
> > hot
> > > deploy the same application with same or different name ( say
> > hello.war |
> > > hello2.war | hello2 directory ) , the server throws an exception
> > saying
> > > there exists already an application deployed , But doesn't delete the
> > module
> > > ( hello.war | hello2.war | hello2 directory) from hot deploy
> > directory
> > > thus the next time the server starts , it tries to deploy the same
> > module
> > > once again.
> > >
> > > I think the better option in this case would be to delete the
> > > unsuccessfully hot deployed application file or directory from hot
> > deploy
> > > directory and show some message.
> > >
> > > With Thanks and Regards,
> > > Mansoor
> >
>
>
Re: When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory.
Posted by Mansoor <ma...@gmail.com>.
Thanks Aaron for your prompt response ,
I was thinking , whether we can put this feature into our geronimo.
Infact i have written a piece of code , that removes this problem.should i
need to raise a jira and submit as a patch ?
On 4/5/06, Aaron Mulder <am...@alumni.princeton.edu> wrote:
>
> OK. For now, we recommend that you only use one deployment method on
> any given application -- always use the hot deploy dir, or always use
> the command-line deploy tool, etc. It's definitely possible to
> confuse things at the moment by switching techniques for the same
> application or module.
>
> Thanks,
> Aaron
>
> On 4/5/06, lak n <ma...@gmail.com> wrote:
> >
> >
> > Hot deployment Issue :
> > When already an application module say (hello.war) is deployed
> (either
> > by using manually or hot deploy procedure ) , And when some one try to
> hot
> > deploy the same application with same or different name ( say hello.war|
> > hello2.war | hello2 directory ) , the server throws an exception saying
> > there exists already an application deployed , But doesn't delete the
> module
> > ( hello.war | hello2.war | hello2 directory) from hot deploy directory
> > thus the next time the server starts , it tries to deploy the same
> module
> > once again.
> >
> > I think the better option in this case would be to delete the
> > unsuccessfully hot deployed application file or directory from hot
> deploy
> > directory and show some message.
> >
> > With Thanks and Regards,
> > Mansoor
>
Re: When already deployed application is hot deployed once gain , Server doesn't delete the module from hot deployed directory.
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
OK. For now, we recommend that you only use one deployment method on
any given application -- always use the hot deploy dir, or always use
the command-line deploy tool, etc. It's definitely possible to
confuse things at the moment by switching techniques for the same
application or module.
Thanks,
Aaron
On 4/5/06, lak n <ma...@gmail.com> wrote:
>
>
> Hot deployment Issue :
> When already an application module say (hello.war) is deployed (either
> by using manually or hot deploy procedure ) , And when some one try to hot
> deploy the same application with same or different name ( say hello.war |
> hello2.war | hello2 directory ) , the server throws an exception saying
> there exists already an application deployed , But doesn't delete the module
> ( hello.war | hello2.war | hello2 directory) from hot deploy directory
> thus the next time the server starts , it tries to deploy the same module
> once again.
>
> I think the better option in this case would be to delete the
> unsuccessfully hot deployed application file or directory from hot deploy
> directory and show some message.
>
> With Thanks and Regards,
> Mansoor