[
https://issues.apache.org/jira/browse/GERONIMO-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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.
