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