Deploying to multiple instances of G
Currently when an app is deployed to an instance of G (say A), it show up as 'stopped' in other instances. IIRC the relevant config.xml had load=false for this config. If the app is deleted from A and all the servers are shutdown. The other servers can not be started (NoSuchConfigException) because the config (app) has been removed from the repository. What should be the correct behavior? Thanks Anita Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs
Re: Deploying to multiple instances of G
On Dec 4, 2007 7:36 PM, Anita Kulshreshtha [EMAIL PROTECTED] wrote: Currently when an app is deployed to an instance of G (say A), it show up as 'stopped' in other instances. IIRC the relevant config.xml had load=false for this config. There shouldn't be any entry for this app in config.xml in the other instances of the server. Atleast it does not get added at deployment time. Even if it gets added with load=false, it does not result in a server startup failure whether or not the app is uninstalled from the server instance it is originally installed. If the app is deleted from A and all the servers are shutdown. The other servers can not be started (NoSuchConfigException) because the config (app) has been removed from the repository. What should be the correct behavior? If the app is installed from instance A and uninstalled from instance B then instance A is in trouble. I raised this concern a while ago and David Jencks said it is expected. As long as the app is installed and uninstalled from the same server instance, it should not (and does not currently) affect other instances. Thanks Anita Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs
Re: Deploying to multiple instances of G
yes, I uninstalled it from the wrong server despite being aware of the behavior... Another version of the same problem is that the same app can not be deployed in another instance. am I correct? Thanks Anita --- Vamsavardhana Reddy [EMAIL PROTECTED] wrote: On Dec 4, 2007 7:36 PM, Anita Kulshreshtha [EMAIL PROTECTED] wrote: Currently when an app is deployed to an instance of G (say A), it show up as 'stopped' in other instances. IIRC the relevant config.xml had load=false for this config. There shouldn't be any entry for this app in config.xml in the other instances of the server. Atleast it does not get added at deployment time. Even if it gets added with load=false, it does not result in a server startup failure whether or not the app is uninstalled from the server instance it is originally installed. If the app is deleted from A and all the servers are shutdown. The other servers can not be started (NoSuchConfigException) because the config (app) has been removed from the repository. What should be the correct behavior? If the app is installed from instance A and uninstalled from instance B then instance A is in trouble. I raised this concern a while ago and David Jencks said it is expected. As long as the app is installed and uninstalled from the same server instance, it should not (and does not currently) affect other instances. Thanks Anita Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
Re: Deploying to multiple instances of G
Yes, the application can not be installed from other instances as all the instances are sharing the same repository. But, nothing prevents you from starting the app in the other instances. Only thing is that before you to uninstall the application from one instance, it has to be stopped in the other instances or else those instances will end up with startup failure. I have not experimented with each instance using its own repository for applications and using common repository for core components. In this case, one may have to use command line deployer and use the target option to specify the repo to which app is to be deployed. ++Vamsi On Dec 4, 2007 9:29 PM, Anita Kulshreshtha [EMAIL PROTECTED] wrote: yes, I uninstalled it from the wrong server despite being aware of the behavior... Another version of the same problem is that the same app can not be deployed in another instance. am I correct? Thanks Anita --- Vamsavardhana Reddy [EMAIL PROTECTED] wrote: On Dec 4, 2007 7:36 PM, Anita Kulshreshtha [EMAIL PROTECTED] wrote: Currently when an app is deployed to an instance of G (say A), it show up as 'stopped' in other instances. IIRC the relevant config.xml had load=false for this config. There shouldn't be any entry for this app in config.xml in the other instances of the server. Atleast it does not get added at deployment time. Even if it gets added with load=false, it does not result in a server startup failure whether or not the app is uninstalled from the server instance it is originally installed. If the app is deleted from A and all the servers are shutdown. The other servers can not be started (NoSuchConfigException) because the config (app) has been removed from the repository. What should be the correct behavior? If the app is installed from instance A and uninstalled from instance B then instance A is in trouble. I raised this concern a while ago and David Jencks said it is expected. As long as the app is installed and uninstalled from the same server instance, it should not (and does not currently) affect other instances. Thanks Anita Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
