geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ashish Jain <>
Subject Re: Applications are rendered unavailable when resources dependencies are redeployed
Date Tue, 13 Apr 2010 14:34:10 GMT
Hi Amit,

I think you may want to try this scenario out. You can try looking onto the
redeploy functionality and try a similar scenario and see the behavior.
Look into classses ConfigurationStatus, ConfigurationModel and see how the
childs are being stopped.

IIUC I do not see much issue in keeping the app up while the dependencies
are down only if the errors are logged properly. Probably others can
provide better insight on this.


On Tue, Apr 13, 2010 at 1:51 PM, Amit Puri <> wrote:

> Hi All
> In a large enterprise where App's are deployed on a number of Geronimo
> servers, we are facing some issues while redeploying the dependencies. Here
> is the outline of the issue being faced:
> When one of its dependencies is being redeployed, a running application is
> stopped. In config.xml too, load attribute is set to false. Let's take an
> example, Application A is depending on dbpool B. While you redeploy B,
> Geronimo will stop A and redeploy dbpool B but it will not restart A. We
> have to manually start the app by using the deploy script with the start
> command or set load to true in config.xml and restart the server.
> As per standard design of application life-cycle in Geronimo, when we
> redeploy the dependency of an application, it will unload the application
> first and redeploy the dependencies, it will  keep load="false" to app
> module in config.xml. But as per our requirement, we need to keep
> applications loaded in an executable state even when its dependencies are
> being redeployed. Is it feasible to do in Geronimo? Please comment.
> Thanks
> Amit

View raw message