[jira] Closed: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain closed GERONIMO-4795. - Resolution: Won't Fix Closing it. Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances -- Key: GERONIMO-4795 URL: https://issues.apache.org/jira/browse/GERONIMO-4795 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.3, 2.1.4 Environment: Windows XP G 214 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: Wish List Attachments: GERONIMO-4795.patch, MultipleServer-1.0.jar, plan.xml 1) Setup another geronimo instance out of the same installation directory. 2) Deploy an applicaton to one instance. This will result in entry being created in config.xml for both the instances 3) Undeploy the application. This results in entry being removed from config.xml of one instance and other instance still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain updated GERONIMO-4795: -- Fix Version/s: (was: 2.1.5) Wish List Moving to wish list as no action is required for g 2.1.5 release. Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances -- Key: GERONIMO-4795 URL: https://issues.apache.org/jira/browse/GERONIMO-4795 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.3, 2.1.4 Environment: Windows XP G 214 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: Wish List Attachments: GERONIMO-4795.patch, MultipleServer-1.0.jar, plan.xml 1) Setup another geronimo instance out of the same installation directory. 2) Deploy an applicaton to one instance. This will result in entry being created in config.xml for both the instances 3) Undeploy the application. This results in entry being removed from config.xml of one instance and other instance still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12835065#action_12835065 ] David Jencks commented on GERONIMO-4795: I'm reluctant to include either of the approaches in geronimo because I think they are founded on inappropriate ways of dealing with multiple servers sharing a repository. IIUC, in order to get into trouble, you have to: 1. have more than one server running off the same repository. (this is ok to do) 2. install a plugin into the repository and onto one of the servers (whether by deploying an app or installing a plugin, doesn't matter) 3. start the plugin on the other server(s) (all of this is fine so far) 4. uninstall the app from one of the servers without stopping it on the other servers first. This is a no-no. IIUC if you stop the app on all servers and then uninstall it everything is fine. Also IIUC the big problem is if you stop and try to restart the broken server that thinks the app is still there. I think both approaches have the problem that if the server is stopped before cleanup takes place you still can't restart it. I think a better approach is to manage the start/stop state of all the apps as a plugin farm of some kind as is possible in 2.2. Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances -- Key: GERONIMO-4795 URL: https://issues.apache.org/jira/browse/GERONIMO-4795 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.3, 2.1.4 Environment: Windows XP G 214 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5 Attachments: GERONIMO-4795.patch, MultipleServer-1.0.jar, plan.xml 1) Setup another geronimo instance out of the same installation directory. 2) Deploy an applicaton to one instance. This will result in entry being created in config.xml for both the instances 3) Undeploy the application. This results in entry being removed from config.xml of one instance and other instance still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12831470#action_12831470 ] Ashish Jain commented on GERONIMO-4795: --- I have written a new Timer gbean which will periodically scan the repository and will accordingly update the config.xml. The time interval in which the gbean will scan the repository is configurable. Please review the uploaded code. Thanks Ashish Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances -- Key: GERONIMO-4795 URL: https://issues.apache.org/jira/browse/GERONIMO-4795 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.3, 2.1.4 Environment: Windows XP G 214 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5 Attachments: GERONIMO-4795.patch, MultipleServer-1.0.jar, plan.xml 1) Setup another geronimo instance out of the same installation directory. 2) Deploy an applicaton to one instance. This will result in entry being created in config.xml for both the instances 3) Undeploy the application. This results in entry being removed from config.xml of one instance and other instance still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain updated GERONIMO-4795: -- Attachment: MultipleServer-1.0.jar Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances -- Key: GERONIMO-4795 URL: https://issues.apache.org/jira/browse/GERONIMO-4795 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.3, 2.1.4 Environment: Windows XP G 214 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5 Attachments: GERONIMO-4795.patch, MultipleServer-1.0.jar, plan.xml 1) Setup another geronimo instance out of the same installation directory. 2) Deploy an applicaton to one instance. This will result in entry being created in config.xml for both the instances 3) Undeploy the application. This results in entry being removed from config.xml of one instance and other instance still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain updated GERONIMO-4795: -- Attachment: plan.xml Attaching the MultipleServer-1.0.jar and the plan file. Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances -- Key: GERONIMO-4795 URL: https://issues.apache.org/jira/browse/GERONIMO-4795 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.3, 2.1.4 Environment: Windows XP G 214 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5 Attachments: GERONIMO-4795.patch, MultipleServer-1.0.jar, plan.xml 1) Setup another geronimo instance out of the same installation directory. 2) Deploy an applicaton to one instance. This will result in entry being created in config.xml for both the instances 3) Undeploy the application. This results in entry being removed from config.xml of one instance and other instance still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain updated GERONIMO-4795: -- Fix Version/s: (was: Wish List) 2.1.5 Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances -- Key: GERONIMO-4795 URL: https://issues.apache.org/jira/browse/GERONIMO-4795 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.3, 2.1.4 Environment: Windows XP G 214 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.1.5 Attachments: GERONIMO-4795.patch 1) Setup another geronimo instance out of the same installation directory. 2) Deploy an applicaton to one instance. This will result in entry being created in config.xml for both the instances 3) Undeploy the application. This results in entry being removed from config.xml of one instance and other instance still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12796751#action_12796751 ] Ashish Jain commented on GERONIMO-4795: --- Can someone help review and provide comments over the patch? Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances -- Key: GERONIMO-4795 URL: https://issues.apache.org/jira/browse/GERONIMO-4795 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.3, 2.1.4 Environment: Windows XP G 214 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: Wish List Attachments: GERONIMO-4795.patch 1) Setup another geronimo instance out of the same installation directory. 2) Deploy an applicaton to one instance. This will result in entry being created in config.xml for both the instances 3) Undeploy the application. This results in entry being removed from config.xml of one instance and other instance still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated GERONIMO-4795: --- Fix Version/s: (was: 2.2) Wish List Not getting into 2.2, whether or not its a good idea. Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances -- Key: GERONIMO-4795 URL: https://issues.apache.org/jira/browse/GERONIMO-4795 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.3, 2.1.4 Environment: Windows XP G 214 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: Wish List Attachments: GERONIMO-4795.patch 1) Setup another geronimo instance out of the same installation directory. 2) Deploy an applicaton to one instance. This will result in entry being created in config.xml for both the instances 3) Undeploy the application. This results in entry being removed from config.xml of one instance and other instance still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12764726#action_12764726 ] Ashish Jain commented on GERONIMO-4795: --- Please advice if this approach is agreeable. Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances -- Key: GERONIMO-4795 URL: https://issues.apache.org/jira/browse/GERONIMO-4795 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.3, 2.1.4 Environment: Windows XP G 214 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2 Attachments: GERONIMO-4795.patch 1) Setup another geronimo instance out of the same installation directory. 2) Deploy an applicaton to one instance. This will result in entry being created in config.xml for both the instances 3) Undeploy the application. This results in entry being removed from config.xml of one instance and other instance still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Jain updated GERONIMO-4795: -- Attachment: GERONIMO-4795.patch Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances -- Key: GERONIMO-4795 URL: https://issues.apache.org/jira/browse/GERONIMO-4795 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.3, 2.1.4 Environment: Windows XP G 214 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2 Attachments: GERONIMO-4795.patch 1) Setup another geronimo instance out of the same installation directory. 2) Deploy an applicaton to one instance. This will result in entry being created in config.xml for both the instances 3) Undeploy the application. This results in entry being removed from config.xml of one instance and other instance still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12763156#action_12763156 ] Ashish Jain commented on GERONIMO-4795: --- Just an explanation : Let us suppose we have two instances of server instance A and instance B. Instance B is created by copying var/* to myserver/var*. Step 1: Deploy an application to the server instance A. The application goes to the common repository. Access the config.xml for instance A...entry is created for the application deployed. Access the config.xml for instance Bno entry created. Step 2: Now access the admin console for instance B-- EAR or WAR portlet ( depending on the type of the application). Now check the config.xml for instance B. An entry for the application is created in the config.xml however with load=false. Step 3: Start the application in instance B config.xml entry changes to load=true. Step 4: Uninstall the application from instance A..Admin console entry is removed for entry A as well as B. Verify the config.xml for A and B. Entry from A is removed however entry from B is not removed. So this is the first problem we hit. I am uploading a patch for this issue. However this works only when the admin console EAR or WAR portlet is accessed for that particular instance. In case the admin console from instance B is not accessed the entry will still remain however there are no side effects. Second problem comes when instance B is restarted. If instance B is restarted after un-installation of application but w/o accessing the admin console than in that case the entry in config.xml for instance B will still remain present so restart will fail as instance B will not be able to to find the module in the configuration store. So to fix this issue another patch has to be generated I hope by using the shutdown hooks whose run method will just do the same thing as the patch uploaded, however just before shutdown. In my opinion these two fixes will take care of the multiple server instances w/o introducing much complexity. Please review the approach. The patch is just a rough one and I will create a neat one if the approach is agreeable. Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances -- Key: GERONIMO-4795 URL: https://issues.apache.org/jira/browse/GERONIMO-4795 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.3, 2.1.4 Environment: Windows XP G 214 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2 Attachments: GERONIMO-4795.patch 1) Setup another geronimo instance out of the same installation directory. 2) Deploy an applicaton to one instance. This will result in entry being created in config.xml for both the instances 3) Undeploy the application. This results in entry being removed from config.xml of one instance and other instance still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4787) EJB module cannot be removed cleanly if uninstalling an application with ejb modules
[ https://issues.apache.org/jira/browse/GERONIMO-4787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-4787. -- Resolution: Fixed duplicated. EJB module cannot be removed cleanly if uninstalling an application with ejb modules Key: GERONIMO-4787 URL: https://issues.apache.org/jira/browse/GERONIMO-4787 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB Affects Versions: 2.2 Environment: Geronimo build: 2009.08.06 Platform: any OS JDK: IBM JDK 6 Reporter: Forrest Xia Priority: Critical Steps: 1. get an installable daytrader sample 2. deploy it 3. undeploy it and then redeploy it Problem: this error appears on console output: 2009-08-07 09:47:40,034 ERROR [DeploymentPortlet] The application was not successfully started start of org.apache.geronimo.daytrader/daytrader/2.1.1.2/car failed org.apache.geronimo.kernel.config.LifecycleException: start of org.apache.geronimo.daytrader/daytrader/2.1.1.2/car failed at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:562) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:527) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:815) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$2d8a8789.startConfiguration(generated) at org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCommand.java:67) at java.lang.Thread.run(Thread.java:735) Caused by: org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start exception at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:522) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:190) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:546) ... 14 more Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: Configuration org.apache.geronimo.daytrader/daytrader/2.1.1.2/car failed to start due to the following reasons: The service EJBModule=dt-ejb.jar,J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=StatelessSessionBean,name=DirectSLSBBean did not start because org.apache.geronimo.daytrader/daytrader/2.1.1.2/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start. The service EJBModule=dt-ejb.jar,J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=StatelessSessionBean,name=TradeSLSBBean did not start because org.apache.geronimo.daytrader/daytrader/2.1.1.2/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start. The service EJBModule=dt-ejb.jar,J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=MessageDrivenBean,name=DTBroker3MDB did not start because org.apache.geronimo.daytrader/daytrader/2.1.1.2/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start. The service EJBModule=dt-ejb.jar,J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=MessageDrivenBean,name=DTStreamer3MDB did not start because org.apache.geronimo.daytrader/daytrader/2.1.1.2/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start. The service J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start because Creating application failed: /home/forrestxm/temp/g22ss/var/temp/geronimo
[jira] Commented: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744038#action_12744038 ] Ashish Jain commented on GERONIMO-4795: --- Yes I am referring to 2.1.x and in 2.1.x we have to use the copying var/* mechanism to create multiple server instances. However my setup is pre-set to have another instance up and the operations like deploy/undeploy are performed after the multiple server setup is ready. However as David has suggested that there are no compelling use cases where this is being used or can be used. IMO there are two ways to use it as far as 2.1.x is considered 1) Set up each server with its own repository so that the undeploy/deploy can be performed individually. 2) As David has suggested that there are not so imp scenarios in which this feature can be used I would suggest to use this with a cluster setup to get the best out of this feature. Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances -- Key: GERONIMO-4795 URL: https://issues.apache.org/jira/browse/GERONIMO-4795 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.3, 2.1.4 Environment: Windows XP G 214 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2 1) Setup another geronimo instance out of the same installation directory. 2) Deploy an applicaton to one instance. This will result in entry being created in config.xml for both the instances 3) Undeploy the application. This results in entry being removed from config.xml of one instance and other instance still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12743951#action_12743951 ] Kevan Miller commented on GERONIMO-4795: Right. My 2) should have referred to install, not deploy. I was thinking about our 2.1.x support, not 2.2. So, deploy/new-instance would not be available... Copying var/* is the mechanism for creating multiple server instances on 2.1.x. I'm assuming that Ashish is referring to 2.1, not 2.2 Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances -- Key: GERONIMO-4795 URL: https://issues.apache.org/jira/browse/GERONIMO-4795 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.3, 2.1.4 Environment: Windows XP G 214 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2 1) Setup another geronimo instance out of the same installation directory. 2) Deploy an applicaton to one instance. This will result in entry being created in config.xml for both the instances 3) Undeploy the application. This results in entry being removed from config.xml of one instance and other instance still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4787) EJB module cannot be removed cleanly if uninstalling an application with ejb modules
[ https://issues.apache.org/jira/browse/GERONIMO-4787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12743953#action_12743953 ] Rex Wang commented on GERONIMO-4787: Thanks for pointing out this. I did not notice the previous commit by you... EJB module cannot be removed cleanly if uninstalling an application with ejb modules Key: GERONIMO-4787 URL: https://issues.apache.org/jira/browse/GERONIMO-4787 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB Affects Versions: 2.2 Environment: Geronimo build: 2009.08.06 Platform: any OS JDK: IBM JDK 6 Reporter: Forrest Xia Priority: Critical Steps: 1. get an installable daytrader sample 2. deploy it 3. undeploy it and then redeploy it Problem: this error appears on console output: 2009-08-07 09:47:40,034 ERROR [DeploymentPortlet] The application was not successfully started start of org.apache.geronimo.daytrader/daytrader/2.1.1.2/car failed org.apache.geronimo.kernel.config.LifecycleException: start of org.apache.geronimo.daytrader/daytrader/2.1.1.2/car failed at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:562) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:527) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:815) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$2d8a8789.startConfiguration(generated) at org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCommand.java:67) at java.lang.Thread.run(Thread.java:735) Caused by: org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start exception at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:522) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:190) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:546) ... 14 more Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: Configuration org.apache.geronimo.daytrader/daytrader/2.1.1.2/car failed to start due to the following reasons: The service EJBModule=dt-ejb.jar,J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=StatelessSessionBean,name=DirectSLSBBean did not start because org.apache.geronimo.daytrader/daytrader/2.1.1.2/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start. The service EJBModule=dt-ejb.jar,J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=StatelessSessionBean,name=TradeSLSBBean did not start because org.apache.geronimo.daytrader/daytrader/2.1.1.2/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start. The service EJBModule=dt-ejb.jar,J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=MessageDrivenBean,name=DTBroker3MDB did not start because org.apache.geronimo.daytrader/daytrader/2.1.1.2/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start. The service EJBModule=dt-ejb.jar,J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=MessageDrivenBean,name=DTStreamer3MDB did not start because org.apache.geronimo.daytrader/daytrader/2.1.1.2/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start. The service J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did
[jira] Commented: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12743725#action_12743725 ] David Jencks commented on GERONIMO-4795: IMO the techniques you mention are usually not the best way to deal with multiple server instances. (2) doesn't make any sense to me -- a plugin has already made use of a deployment plan, and is in a state where an additional deployment plan cannot be interpreted. Recommended (by me) ways to deal with more than one server instance in an installation: a. add a new server instance using the new server instance command: this will create the base directory and proceed to install all the plugins installed in the source server. Since the repo is shared, nothing will change in the repo, but the plugins being installed into the new server will set up the config.xml, and related files and unpack any plugin specific content into the appropriate places. b. Giving an existing additional server instance with a plugin present in the geronimo repo but not installed in the additional instance, installing it into the additional instance will add the config.xml content and related file content and unpack any files needed. if you copy a var directory per your (1) you will get any local changes and edits and data that happen to be present in the server instance, so the results are inherently unpredictable. (a) produces a fresh server without local modifications. Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances -- Key: GERONIMO-4795 URL: https://issues.apache.org/jira/browse/GERONIMO-4795 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.3, 2.1.4 Environment: Windows XP G 214 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2 1) Setup another geronimo instance out of the same installation directory. 2) Deploy an applicaton to one instance. This will result in entry being created in config.xml for both the instances 3) Undeploy the application. This results in entry being removed from config.xml of one instance and other instance still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances -- Key: GERONIMO-4795 URL: https://issues.apache.org/jira/browse/GERONIMO-4795 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: commands Affects Versions: 2.1.4, 2.1.3 Environment: Windows XP G 214 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2 1) Setup another geronimo instance out of the same installation directory. 2) Deploy an applicaton to one instance. This will result in entry being created in config.xml for both the instances 3) Undeploy the application. This results in entry being removed from config.xml of one instance and other instance still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4787) EJB module cannot be removed cleanly if uninstalling an application with ejb modules
[ https://issues.apache.org/jira/browse/GERONIMO-4787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12743155#action_12743155 ] Rex Wang commented on GERONIMO-4787: can not recreate in a simple ear that contain a simple mdb, so this happens only in daytrader project, not a common issues. I have to look into the code in daytrader -Rex EJB module cannot be removed cleanly if uninstalling an application with ejb modules Key: GERONIMO-4787 URL: https://issues.apache.org/jira/browse/GERONIMO-4787 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB Affects Versions: 2.2 Environment: Geronimo build: 2009.08.06 Platform: any OS JDK: IBM JDK 6 Reporter: Forrest Xia Priority: Critical Steps: 1. get an installable daytrader sample 2. deploy it 3. undeploy it and then redeploy it Problem: this error appears on console output: 2009-08-07 09:47:40,034 ERROR [DeploymentPortlet] The application was not successfully started start of org.apache.geronimo.daytrader/daytrader/2.1.1.2/car failed org.apache.geronimo.kernel.config.LifecycleException: start of org.apache.geronimo.daytrader/daytrader/2.1.1.2/car failed at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:562) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:527) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:815) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$2d8a8789.startConfiguration(generated) at org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCommand.java:67) at java.lang.Thread.run(Thread.java:735) Caused by: org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start exception at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:522) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:190) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:546) ... 14 more Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: Configuration org.apache.geronimo.daytrader/daytrader/2.1.1.2/car failed to start due to the following reasons: The service EJBModule=dt-ejb.jar,J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=StatelessSessionBean,name=DirectSLSBBean did not start because org.apache.geronimo.daytrader/daytrader/2.1.1.2/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start. The service EJBModule=dt-ejb.jar,J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=StatelessSessionBean,name=TradeSLSBBean did not start because org.apache.geronimo.daytrader/daytrader/2.1.1.2/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start. The service EJBModule=dt-ejb.jar,J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=MessageDrivenBean,name=DTBroker3MDB did not start because org.apache.geronimo.daytrader/daytrader/2.1.1.2/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start. The service EJBModule=dt-ejb.jar,J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=MessageDrivenBean,name=DTStreamer3MDB did not start because org.apache.geronimo.daytrader/daytrader/2.1.1.2/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start. The service
[jira] Commented: (GERONIMO-4787) EJB module cannot be removed cleanly if uninstalling an application with ejb modules
[ https://issues.apache.org/jira/browse/GERONIMO-4787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12743157#action_12743157 ] Ivan commented on GERONIMO-4787: This issue should be the same with Geronimo-4791. I think it has already been fixed. EJB module cannot be removed cleanly if uninstalling an application with ejb modules Key: GERONIMO-4787 URL: https://issues.apache.org/jira/browse/GERONIMO-4787 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB Affects Versions: 2.2 Environment: Geronimo build: 2009.08.06 Platform: any OS JDK: IBM JDK 6 Reporter: Forrest Xia Priority: Critical Steps: 1. get an installable daytrader sample 2. deploy it 3. undeploy it and then redeploy it Problem: this error appears on console output: 2009-08-07 09:47:40,034 ERROR [DeploymentPortlet] The application was not successfully started start of org.apache.geronimo.daytrader/daytrader/2.1.1.2/car failed org.apache.geronimo.kernel.config.LifecycleException: start of org.apache.geronimo.daytrader/daytrader/2.1.1.2/car failed at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:562) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:527) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:815) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$2d8a8789.startConfiguration(generated) at org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCommand.java:67) at java.lang.Thread.run(Thread.java:735) Caused by: org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start exception at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:522) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:190) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:546) ... 14 more Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: Configuration org.apache.geronimo.daytrader/daytrader/2.1.1.2/car failed to start due to the following reasons: The service EJBModule=dt-ejb.jar,J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=StatelessSessionBean,name=DirectSLSBBean did not start because org.apache.geronimo.daytrader/daytrader/2.1.1.2/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start. The service EJBModule=dt-ejb.jar,J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=StatelessSessionBean,name=TradeSLSBBean did not start because org.apache.geronimo.daytrader/daytrader/2.1.1.2/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start. The service EJBModule=dt-ejb.jar,J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=MessageDrivenBean,name=DTBroker3MDB did not start because org.apache.geronimo.daytrader/daytrader/2.1.1.2/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start. The service EJBModule=dt-ejb.jar,J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=MessageDrivenBean,name=DTStreamer3MDB did not start because org.apache.geronimo.daytrader/daytrader/2.1.1.2/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start. The service J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did
[jira] Commented: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12743261#action_12743261 ] David Jencks commented on GERONIMO-4795: I don't think we should try to fix this. IMO the proper use of servers is to construct them with the plugins you want, and possibly add more plugins. However removing plugins is not generally the reverse of adding them. For instance we don't try to delete data files installed when the plugin was unpacked, remove config.xml entries, config-substitutions.properties, or artifact aliases. Trying to change this will introduce near infinite complexity for no good reason. Just dont' uninstall apps, assemble a new server instead. In particular, I think that altering the behavior for mulitple server instances here would require some kind of registry of all the servers running off of a particular geronimo repository. I don't think there's any need for this. I'm not aware of any compelling uses for multiple server instances so I'm very much against introducing more complexity to make a small aspect of uninstalling plugins slightly less problematical. Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances -- Key: GERONIMO-4795 URL: https://issues.apache.org/jira/browse/GERONIMO-4795 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.3, 2.1.4 Environment: Windows XP G 214 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2 1) Setup another geronimo instance out of the same installation directory. 2) Deploy an applicaton to one instance. This will result in entry being created in config.xml for both the instances 3) Undeploy the application. This results in entry being removed from config.xml of one instance and other instance still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4795) Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
[ https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12743464#action_12743464 ] Kevan Miller commented on GERONIMO-4795: That may be how you *think* the server should be used. Although I think a disposable server model for using Geronimo is an excellent technique, it's not the only technique. I certainly talk with users who have decided not to manage their Geronimo environment in this way... So, I'm not so quick to dismiss this basic scenario... That said, I think I agree that we should *not* support this undeploy behavior... Seems like there are 3 potential ways to end up in the state described by Ashish: 1) deploy an app/plugin to the default server, then copy var/* to a new server instance 2) deploy a plugin to any server (using the default repository), then deploy the plugin only using a deployment plan (I'm only guessing that this might work). 3) deploy an app/plugin, then manually copy the config.xml changes into the other server's config.xml I don't think these deploy techniques imply that we'll automatically undeploy the apps. User management was required, when deploying the apps to the multiple servers. User Management will be required, when undeploying. Personally, I think the best technique for handling this scenario is with server specific repositories on each server instance. If you want to run the same app on all server instances, you should explicitly deploy/undeploy to each server instance. Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances -- Key: GERONIMO-4795 URL: https://issues.apache.org/jira/browse/GERONIMO-4795 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: commands Affects Versions: 2.1.3, 2.1.4 Environment: Windows XP G 214 Reporter: Ashish Jain Assignee: Ashish Jain Fix For: 2.2 1) Setup another geronimo instance out of the same installation directory. 2) Deploy an applicaton to one instance. This will result in entry being created in config.xml for both the instances 3) Undeploy the application. This results in entry being removed from config.xml of one instance and other instance still has entry of the application in config.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
Hi, I have a setup based on geronimo 2.1.3 and I have created another geronimo instance from existing one using the multiple server instance feature. I had set the following set GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=instance2 and was able to start another instance with a portOffset of 1. Later I deployed a WAR application to one of geronimo instance and can see the application in started state in the instance I have deployed the application and stopped in another instance. I can see an entry in the config.xml as well for both the instances. Another observation in this case is that config.xml for instance2 gets the entry only when I access the admin console WAR portlet for this instance. Later tried undeploying the application. Application is removed from the server repository, application entry is removed from config.xml of the instance I have deployed the application. However the application entry in config.xml of instance2 still remains and is not removed. Just tried debugging this issue and found that LocalAttributeManager.java shows the values with relative to g home for example attributeFile g_home\var\config\config.xml. However it never suggests any value relative to g_home/instance2. ServerOverride.java also works out relative to g_home. Any suggestions on how shall I proceed with this issue will be really helpful. Thanks Ashish
Re: Multiple Server Instances: Uninstalling an application does not remove the entry from config.xml of other server instances
This looks like a problem. You might want to open a JIRA to track it. The config file is resolved based on the server base dir, which should be different for the two instances. You can look into o.a.g.system.serverinfo.BasicServerInfo for more digging. -Jack On Thu, Aug 13, 2009 at 11:50 PM, Ashish Jain ashja...@gmail.com wrote: Hi, I have a setup based on geronimo 2.1.3 and I have created another geronimo instance from existing one using the multiple server instance feature. I had set the following set GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=instance2 and was able to start another instance with a portOffset of 1. Later I deployed a WAR application to one of geronimo instance and can see the application in started state in the instance I have deployed the application and stopped in another instance. I can see an entry in the config.xml as well for both the instances. Another observation in this case is that config.xml for instance2 gets the entry only when I access the admin console WAR portlet for this instance. Later tried undeploying the application. Application is removed from the server repository, application entry is removed from config.xml of the instance I have deployed the application. However the application entry in config.xml of instance2 still remains and is not removed. Just tried debugging this issue and found that LocalAttributeManager.java shows the values with relative to g home for example attributeFile g_home\var\config\config.xml. However it never suggests any value relative to g_home/instance2. ServerOverride.java also works out relative to g_home. Any suggestions on how shall I proceed with this issue will be really helpful. Thanks Ashish
[jira] Created: (GERONIMO-4787) EJB module cannot be removed cleanly if uninstalling an application with ejb modules
EJB module cannot be removed cleanly if uninstalling an application with ejb modules Key: GERONIMO-4787 URL: https://issues.apache.org/jira/browse/GERONIMO-4787 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: OpenEJB Affects Versions: 2.2 Environment: Geronimo build: 2009.08.06 Platform: any OS JDK: IBM JDK 6 Reporter: Forrest Xia Priority: Critical Steps: 1. get an installable daytrader sample 2. deploy it 3. undeploy it and then redeploy it Problem: this error appears on console output: 2009-08-07 09:47:40,034 ERROR [DeploymentPortlet] The application was not successfully started start of org.apache.geronimo.daytrader/daytrader/2.1.1.2/car failed org.apache.geronimo.kernel.config.LifecycleException: start of org.apache.geronimo.daytrader/daytrader/2.1.1.2/car failed at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:562) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:527) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:815) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$2d8a8789.startConfiguration(generated) at org.apache.geronimo.deployment.plugin.local.StartCommand.run(StartCommand.java:67) at java.lang.Thread.run(Thread.java:735) Caused by: org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start exception at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:522) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:190) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:546) ... 14 more Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: Configuration org.apache.geronimo.daytrader/daytrader/2.1.1.2/car failed to start due to the following reasons: The service EJBModule=dt-ejb.jar,J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=StatelessSessionBean,name=DirectSLSBBean did not start because org.apache.geronimo.daytrader/daytrader/2.1.1.2/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start. The service EJBModule=dt-ejb.jar,J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=StatelessSessionBean,name=TradeSLSBBean did not start because org.apache.geronimo.daytrader/daytrader/2.1.1.2/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start. The service EJBModule=dt-ejb.jar,J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=MessageDrivenBean,name=DTBroker3MDB did not start because org.apache.geronimo.daytrader/daytrader/2.1.1.2/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start. The service EJBModule=dt-ejb.jar,J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=MessageDrivenBean,name=DTStreamer3MDB did not start because org.apache.geronimo.daytrader/daytrader/2.1.1.2/car?J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start. The service J2EEApplication=org.apache.geronimo.daytrader/daytrader/2.1.1.2/car,j2eeType=EJBModule,name=dt-ejb.jar did not start because Creating application failed: /home/forrestxm/temp/g22ss/var/temp/geronimo-deploymentUtil450773663474228598.jar: Error deploying 'DTStreamer3MDB'. Exception: class java.lang.NullPointerException: null: null at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:485) ... 16 more
Uninstalling an application
I installed a plugin using 'plugins' portlet in the admin console. It worked as expected. After the plugin is uninstalled it leaves its dependent cars and ears behind. I have tried it from both command line and console. Next time I install the plugin using 'plugins' I get old dependencies. I have to hand delete the stuff from G/repository and edit config.xml to install it correctly. Is there a better way to do this? Thanks Anita Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
Re: Uninstalling an application
I have noticed this irksome behavior too. AFAIK, there isn't a better way. For now, this is a gaping hole in our plugin design. Seems like when a plugin is uninstalled, we'll have to uninstall all the child components recursively. Cheers Prasad On Dec 6, 2007 10:04 AM, Anita Kulshreshtha [EMAIL PROTECTED] wrote: I installed a plugin using 'plugins' portlet in the admin console. It worked as expected. After the plugin is uninstalled it leaves its dependent cars and ears behind. I have tried it from both command line and console. Next time I install the plugin using 'plugins' I get old dependencies. I have to hand delete the stuff from G/repository and edit config.xml to install it correctly. Is there a better way to do this? Thanks Anita Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
Re: Uninstalling an application
Anita Kulshreshtha wrote: I installed a plugin using 'plugins' portlet in the admin console. It worked as expected. After the plugin is uninstalled it leaves its dependent cars and ears behind. I have tried it from both command line and console. Next time I install the plugin using 'plugins' I get old dependencies. I have to hand delete the stuff from G/repository and edit config.xml to install it correctly. Is there a better way to do this? I'm not sure why you would have to edit config.xml. You should be able to uninstall the dependencies manually via command line or the console without the need to modify config.xml manually. The catch is that you need to know what those dependencies are that were installed as a result of your deployment. At the moment there is nothing to remove the dependencies. In order to be able to remove dependencies that were installed we would need to keep some use counts or something similar. We had discussed this a while back with some proposals ... but at the moment nothing is implemented. Joe
Re: Uninstalling an application
--- Joe Bohn [EMAIL PROTECTED] wrote: Anita Kulshreshtha wrote: .. I'm not sure why you would have to edit config.xml. You should be able to uninstall the dependencies manually via command line or the console without the need to modify config.xml manually. The catch is that you need to know what those dependencies are that were installed as a result of your deployment. At the moment there is nothing to remove the dependencies. In order to be able to remove dependencies that were installed we would need to keep some use counts or something similar. We had discussed this a while back with some proposals ... but at the moment nothing is implemented. Joe I was using mrc-server-car. it installs mrc-ds-car and an ear. IIRC, After uninstalling mrc-server-car, shutdown and hand deleting mrc-ds-car, ear from G/repository, the mrc-ds-car was left in config.xml. The server could not be restarted. Thanks Anita Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
Re: Uninstalling an application
Anita Kulshreshtha wrote: --- Joe Bohn [EMAIL PROTECTED] wrote: Anita Kulshreshtha wrote: .. I'm not sure why you would have to edit config.xml. You should be able to uninstall the dependencies manually via command line or the console without the need to modify config.xml manually. The catch is that you need to know what those dependencies are that were installed as a result of your deployment. At the moment there is nothing to remove the dependencies. In order to be able to remove dependencies that were installed we would need to keep some use counts or something similar. We had discussed this a while back with some proposals ... but at the moment nothing is implemented. Joe I was using mrc-server-car. it installs mrc-ds-car and an ear. IIRC, After uninstalling mrc-server-car, shutdown and hand deleting mrc-ds-car, ear from G/repository, the mrc-ds-car was left in config.xml. The server could not be restarted. Why not just uninstall all 3 using the command line or web console so that you don't have to manually delete or edit the config.xml? Joe
[jira] Closed: (GERONIMO-1099) Error Uninstalling an application - cannot re-install application or restart server
[ http://issues.apache.org/jira/browse/GERONIMO-1099?page=all ] Aaron Mulder closed GERONIMO-1099: -- Resolution: Duplicate Error Uninstalling an application - cannot re-install application or restart server --- Key: GERONIMO-1099 URL: http://issues.apache.org/jira/browse/GERONIMO-1099 Project: Geronimo Type: Bug Components: console Versions: 1.0-M5 Reporter: Dave Colasurdo Fix For: 1.0 Using the admin console: 1)Install an application (e.g. servlets-example) 2)Uninstall the application (without first stopping the application) This results in the following error: 13:53:16,772 ERROR [GBeanInstance] GBeanInstance should already be stopped before die() is called: objectName=geronimo.server:J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=Servlet Mapped Filter,WebModule=servlets-examples,j2eeType=WebFilterMapping state=starting 13:53:16,772 ERROR [GBeanInstance] GBeanInstance should already be stopped before die() is called: objectName=geronimo.server:J2EEApplication=null,J2EEServer=geronimo,URLPattern=/servlet/\*,WebFilter=Path Mapped Filter,WebModule=servlets- examples,j2eeType=WebFilterMapping state=starting However, the application is removed from both the directory structure and index.properties is updated. I cannot re-install the application from the console.. The error is Module servlets-examples already exists in the server. Try to undeploy it first or use the redeploy command. There is nothing to undeploy in the list!!! Also, after stopping the server, cannot restart it .. get the following error: Booting Geronimo Kernel (in Java 1.4.2_08)... Starting Geronimo Application Server [***- ] 89% 23s Startup failed org.apache.geronimo.kernel.config.NoSuchConfigException: No configuration with id: servlets-examples at org.apache.geronimo.kernel.config.ConfigurationManagerImpl.load(ConfigurationManagerImpl.java:111) at org.apache.geronimo.kernel.config.ConfigurationManagerImpl.loadRecursive(ConfigurationManagerImpl.java:178) at org.apache.geronimo.kernel.config.ConfigurationManagerImpl.loadRecursive(ConfigurationManagerImpl.java:167) at org.apache.geronimo.kernel.config.ConfigurationManagerImpl$$FastClassByCGLIB$$fbed85d2.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:760) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.kernel.config.ConfigurationManager$$EnhancerByCGLIB$$5ded6b6b.loadRecursive(generated) at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:232) at org.apache.geronimo.system.main.Daemon.init(Daemon.java:78) at org.apache.geronimo.system.main.Daemon.main(Daemon.java:320) Server shutdown begun p failed Server shutdown completed If the application is stopped before being uninstalled (between steps 1 and 2 above) , everything works fine... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1099) Error Uninstalling an application - cannot re-install application or restart server
[ http://issues.apache.org/jira/browse/GERONIMO-1099?page=comments#action_12356532 ] Joe Bohn commented on GERONIMO-1099: It appears that this is not only related to GERONIMO-1047 ... but in fact is the same problem. I have a patch that I'll attach to GERONIMO-1047. Error Uninstalling an application - cannot re-install application or restart server --- Key: GERONIMO-1099 URL: http://issues.apache.org/jira/browse/GERONIMO-1099 Project: Geronimo Type: Bug Components: console Versions: 1.0 Reporter: Dave Colasurdo Using the admin console: 1)Install an application (e.g. servlets-example) 2)Uninstall the application (without first stopping the application) This results in the following error: 13:53:16,772 ERROR [GBeanInstance] GBeanInstance should already be stopped before die() is called: objectName=geronimo.server:J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=Servlet Mapped Filter,WebModule=servlets-examples,j2eeType=WebFilterMapping state=starting 13:53:16,772 ERROR [GBeanInstance] GBeanInstance should already be stopped before die() is called: objectName=geronimo.server:J2EEApplication=null,J2EEServer=geronimo,URLPattern=/servlet/\*,WebFilter=Path Mapped Filter,WebModule=servlets- examples,j2eeType=WebFilterMapping state=starting However, the application is removed from both the directory structure and index.properties is updated. I cannot re-install the application from the console.. The error is Module servlets-examples already exists in the server. Try to undeploy it first or use the redeploy command. There is nothing to undeploy in the list!!! Also, after stopping the server, cannot restart it .. get the following error: Booting Geronimo Kernel (in Java 1.4.2_08)... Starting Geronimo Application Server [***- ] 89% 23s Startup failed org.apache.geronimo.kernel.config.NoSuchConfigException: No configuration with id: servlets-examples at org.apache.geronimo.kernel.config.ConfigurationManagerImpl.load(ConfigurationManagerImpl.java:111) at org.apache.geronimo.kernel.config.ConfigurationManagerImpl.loadRecursive(ConfigurationManagerImpl.java:178) at org.apache.geronimo.kernel.config.ConfigurationManagerImpl.loadRecursive(ConfigurationManagerImpl.java:167) at org.apache.geronimo.kernel.config.ConfigurationManagerImpl$$FastClassByCGLIB$$fbed85d2.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:760) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.kernel.config.ConfigurationManager$$EnhancerByCGLIB$$5ded6b6b.loadRecursive(generated) at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:232) at org.apache.geronimo.system.main.Daemon.init(Daemon.java:78) at org.apache.geronimo.system.main.Daemon.main(Daemon.java:320) Server shutdown begun p failed Server shutdown completed If the application is stopped before being uninstalled (between steps 1 and 2 above) , everything works fine... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1099) Error Uninstalling an application - cannot re-install application or restart server
[ http://issues.apache.org/jira/browse/GERONIMO-1099?page=all ] Joe Bohn updated GERONIMO-1099: --- Geronimo Info: [Patch Available] Fix Version: 1.0 Version: 1.0-M5 (was: 1.0) patch available in 1047 Error Uninstalling an application - cannot re-install application or restart server --- Key: GERONIMO-1099 URL: http://issues.apache.org/jira/browse/GERONIMO-1099 Project: Geronimo Type: Bug Components: console Versions: 1.0-M5 Reporter: Dave Colasurdo Fix For: 1.0 Using the admin console: 1)Install an application (e.g. servlets-example) 2)Uninstall the application (without first stopping the application) This results in the following error: 13:53:16,772 ERROR [GBeanInstance] GBeanInstance should already be stopped before die() is called: objectName=geronimo.server:J2EEApplication=null,J2EEServer=geronimo,Servlet=invoker,WebFilter=Servlet Mapped Filter,WebModule=servlets-examples,j2eeType=WebFilterMapping state=starting 13:53:16,772 ERROR [GBeanInstance] GBeanInstance should already be stopped before die() is called: objectName=geronimo.server:J2EEApplication=null,J2EEServer=geronimo,URLPattern=/servlet/\*,WebFilter=Path Mapped Filter,WebModule=servlets- examples,j2eeType=WebFilterMapping state=starting However, the application is removed from both the directory structure and index.properties is updated. I cannot re-install the application from the console.. The error is Module servlets-examples already exists in the server. Try to undeploy it first or use the redeploy command. There is nothing to undeploy in the list!!! Also, after stopping the server, cannot restart it .. get the following error: Booting Geronimo Kernel (in Java 1.4.2_08)... Starting Geronimo Application Server [***- ] 89% 23s Startup failed org.apache.geronimo.kernel.config.NoSuchConfigException: No configuration with id: servlets-examples at org.apache.geronimo.kernel.config.ConfigurationManagerImpl.load(ConfigurationManagerImpl.java:111) at org.apache.geronimo.kernel.config.ConfigurationManagerImpl.loadRecursive(ConfigurationManagerImpl.java:178) at org.apache.geronimo.kernel.config.ConfigurationManagerImpl.loadRecursive(ConfigurationManagerImpl.java:167) at org.apache.geronimo.kernel.config.ConfigurationManagerImpl$$FastClassByCGLIB$$fbed85d2.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:760) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.kernel.config.ConfigurationManager$$EnhancerByCGLIB$$5ded6b6b.loadRecursive(generated) at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:232) at org.apache.geronimo.system.main.Daemon.init(Daemon.java:78) at org.apache.geronimo.system.main.Daemon.main(Daemon.java:320) Server shutdown begun p failed Server shutdown completed If the application is stopped before being uninstalled (between steps 1 and 2 above) , everything works fine... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
