[ https://issues.apache.org/jira/browse/KARAF-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet updated KARAF-5: -------------------------------- Issue Type: Improvement (was: Bug) > [karaf] admin:create should support a -r, --rmi-registry-port option to allow > the RMI registry port to be configured > --------------------------------------------------------------------------------------------------------------------- > > Key: KARAF-5 > URL: https://issues.apache.org/jira/browse/KARAF-5 > Project: Karaf > Issue Type: Improvement > Reporter: Eoghan Glynn > Assignee: Jean-Baptiste Onofré > > By default the JMX/RMI serviceURL is configured for child instances with the > same RMI registry port as the root instance. > As a result, the monitoring of the child can depend on the live-ness of the > root instance, depending on the startup sequence. > For example if the child is created via "admin:create foo" in the root's > shell, but then started via the $KARAF_HOME/instances/foo/bin/start script, > the child shares the single RMI registry hosted by the root instance. > If the root instance is then stopped, the child may no longer be monitored > over JMX. Even if the root is restarted, the child still cannot be monitored > as there is no auto-reregistration. > Instead it should be possible to create a child instance with an > instance-specific RMI registry port so that its not dependent on an RMI > registry shared with another instance, e.g. "admin:create --rmi-registry-port > 1199 foo" so that rmiRegistryPort=1199 > is configured in > $KARAF_HOME/instances/foo/etc/org.apache.felix.karaf.management.cfg -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.