I've fixed this issue as part of FELIX-1575 by simply using a
different name for each JMX connector to bind in the RMI registry.
Obviously this is not very generic and a better and more generic
mechanism such as the one you describe should be implemented at some
point.
On Mon, Sep 7, 2009 at 21:47
Hi Guillaume,
For the special case of the JMX URI, I wonder would something like the
following approach work:
- allow a parameter to admin:create to specify some extra system
property/ies
- pass those property/ies to the JVM launched via the generated
instances//bin/karaf script
- use this mech
Right, currently, the sshd port for child instances is managed by the
commands, but RMI and HTTP or any other port aren't.
I think it can be done through the command line by connecting to the child
instance and updating the configurations for the config admin, but it's
really tedious and a better w
Hi Folks,
If I launch an admin:create'd instance via admin:start from the master karaf
instance, all is hunky-dorey.
However, if instead the child instance is run from the command line via the
generated instances/ directory tree, then I'm see a port clash on the
JMX RMI connector[1] if the master
