[
https://issues.apache.org/jira/browse/KARAF-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126677#comment-14126677
]
Guillaume Nodet commented on KARAF-3072:
----------------------------------------
Was that fixed already ? I tried with both 2.4 and 3.0 branches, and the
{{etc/org.apache.karaf.management.cfg}} looks good to me, but for the fact that
they child is reusing the RMI registry server from the root instance (which
means if the root instance is stopped, you can't access the child JMX anymore).
> Instance etc files are not sync with the root etc files
> -------------------------------------------------------
>
> Key: KARAF-3072
> URL: https://issues.apache.org/jira/browse/KARAF-3072
> Project: Karaf
> Issue Type: Bug
> Components: karaf-instance
> Affects Versions: 2.4.0, 3.0.1, 4.0.0
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: 2.4.0, 4.0.0, 3.0.2
>
>
> In the instance resources, the files used at instance creation time are not
> sync with the default root instance configuration.
> For instance, etc/org.apache.karaf.management.cfg file doesn't contain the
> rmiRegistryHost in the instances.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
