You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Forrest_Xia <fo...@gmail.com> on 2009/01/10 15:36:25 UTC
Headache deployment failure side-effect issue
Hi all,
One pain point I recently felt is that once a failure deployment happen,
there will be some directories created in the repository, which will stop
the next deployment. I have to manually remove the empty directory in the
repository.
My thought is whether we can improve the deployment mechanism, that is, once
failure detected, all done things could be rollback automatically?
Any thoughts? thanks!
--
View this message in context: http://www.nabble.com/Headache-deployment-failure-side-effect-issue-tp21388698s134p21388698.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
Re: Headache deployment failure side-effect issue
Posted by Donald Woods <dw...@apache.org>.
G4420 has been applied to 2.1.4-SNAPSHOT and trunk. Thanks Ivan for the
patch.
-Donald
viola.lu wrote:
> HI, forrest:
> This problem is reporeted in JIRA
> https://issues.apache.org/jira/browse/GERONIMO-4420 and Ivan provided a path
> yet but not is checked in svn trunk.
> Hope can help you.
> Good Luck!
> Viola.Lu
>
>
>
>
> djencks wrote:
>>
>> On Jan 10, 2009, at 6:36 AM, Forrest_Xia wrote:
>>
>>> Hi all,
>>>
>>> One pain point I recently felt is that once a failure deployment
>>> happen,
>>> there will be some directories created in the repository, which will
>>> stop
>>> the next deployment. I have to manually remove the empty directory
>>> in the
>>> repository.
>>>
>>> My thought is whether we can improve the deployment mechanism, that
>>> is, once
>>> failure detected, all done things could be rollback automatically?
>> That is what is supposed to happen. If you have a reproducible case
>> where it doesn't that should help us fix the bug.
>>
>> thanks
>> david jencks
>>
>>>
>>> Any thoughts? thanks!
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Headache-deployment-failure-side-effect-issue-tp21388698s134p21388698.html
>>> Sent from the Apache Geronimo - Dev mailing list archive at
>>> Nabble.com.
>>>
>>
>>
>
Re: Headache deployment failure side-effect issue
Posted by Forrest_Xia <fo...@gmail.com>.
Yep, Viola, the jira fix is what I am expecting :-), hope it could be
included in AG 2.2 release. Thanks for pointing it out
To David, -B, thanks for replying. My post background story is, when I use
Eclipse and GEP to develop some JEE applications, inevitably I would make
some bad configurations, that leads the deployment failure, then I update my
configuration. The GEP will automatically redeploy the app, once there is a
bad deployment previously, the auto-redeploy will fail, and report something
like "One module directory is not empty in the repository", and stop its
deployment.
The Viola's point-out seems fixing my encountered issue, but who knows until
I can verify it :)
Forrest
--
View this message in context: http://www.nabble.com/Headache-deployment-failure-side-effect-issue-tp21388698s134p21410198.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
Re: Headache deployment failure side-effect issue
Posted by "viola.lu" <vi...@gmail.com>.
HI, forrest:
This problem is reporeted in JIRA
https://issues.apache.org/jira/browse/GERONIMO-4420 and Ivan provided a path
yet but not is checked in svn trunk.
Hope can help you.
Good Luck!
Viola.Lu
djencks wrote:
>
>
> On Jan 10, 2009, at 6:36 AM, Forrest_Xia wrote:
>
>>
>> Hi all,
>>
>> One pain point I recently felt is that once a failure deployment
>> happen,
>> there will be some directories created in the repository, which will
>> stop
>> the next deployment. I have to manually remove the empty directory
>> in the
>> repository.
>>
>> My thought is whether we can improve the deployment mechanism, that
>> is, once
>> failure detected, all done things could be rollback automatically?
>
> That is what is supposed to happen. If you have a reproducible case
> where it doesn't that should help us fix the bug.
>
> thanks
> david jencks
>
>>
>>
>> Any thoughts? thanks!
>> --
>> View this message in context:
>> http://www.nabble.com/Headache-deployment-failure-side-effect-issue-tp21388698s134p21388698.html
>> Sent from the Apache Geronimo - Dev mailing list archive at
>> Nabble.com.
>>
>
>
>
--
View this message in context: http://www.nabble.com/Headache-deployment-failure-side-effect-issue-tp21388698s134p21398332.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
Re: Headache deployment failure side-effect issue
Posted by David Jencks <da...@yahoo.com>.
On Jan 10, 2009, at 6:36 AM, Forrest_Xia wrote:
>
> Hi all,
>
> One pain point I recently felt is that once a failure deployment
> happen,
> there will be some directories created in the repository, which will
> stop
> the next deployment. I have to manually remove the empty directory
> in the
> repository.
>
> My thought is whether we can improve the deployment mechanism, that
> is, once
> failure detected, all done things could be rollback automatically?
That is what is supposed to happen. If you have a reproducible case
where it doesn't that should help us fix the bug.
thanks
david jencks
>
>
> Any thoughts? thanks!
> --
> View this message in context: http://www.nabble.com/Headache-deployment-failure-side-effect-issue-tp21388698s134p21388698.html
> Sent from the Apache Geronimo - Dev mailing list archive at
> Nabble.com.
>
Re: Headache deployment failure side-effect issue
Posted by bongosdude <bo...@gmail.com>.
Hmm, I did not realize these empty directory. Can you detail what you
encounter so that I learn what you faced too?
Thanks
-B
Forrest_Xia wrote:
>
> Hi all,
>
> One pain point I recently felt is that once a failure deployment happen,
> there will be some directories created in the repository, which will stop
> the next deployment. I have to manually remove the empty directory in the
> repository.
>
> My thought is whether we can improve the deployment mechanism, that is,
> once failure detected, all done things could be rollback automatically?
>
> Any thoughts? thanks!
>
-----
B Amigo:super:
--
View this message in context: http://www.nabble.com/Headache-deployment-failure-side-effect-issue-tp21388698s134p21389914.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.