[
https://issues.apache.org/activemq/browse/SMX4KNL-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48856#action_48856
]
Jamie Goodyear commented on SMX4KNL-169:
----------------------------------------
h5. JMX port bind exception.
After experimenting with various ways of setting jmx port usage I believe that
we may have to go with configuring the JMX port separately for each SMX
instance on a single host.
* The command to use JMX is passed into the JVM at startup time, we'd have to
delay JVM startup to avoid a port conflict if instances were to share a common
port.
** Separate full installations would only require a manual update of port
allocation.
** Instances created from admin console may have their ports pre-allocated.
Currently each instance references the parent's 'servicemix' run script, these
scripts will have to be copy & filtered for each created instance (similar to
how ssh ports are currently allocated). The JMX port for an instance would need
to be reported for ease of use via console.
* Authentication would be defaulted to false.
h6. SSH port
We already posses the ability to configure the ssh port via
org.apache.servicemix.shell.cfg.
* When instances are created from the admin console a port is automatically
assigned.
* Separate full installations already require manual ssh port configuration in
shell.cfg.
h6. Run Level combinations.
As noted above different runtime behaviors will be observed based upon bundle
start levels. A best practices document may be required in the users guide to
help determine base settings for 'servicemix.lock.level'.
> Use the start level to implement the container level locking
> ------------------------------------------------------------
>
> Key: SMX4KNL-169
> URL: https://issues.apache.org/activemq/browse/SMX4KNL-169
> Project: ServiceMix Kernel
> Issue Type: Improvement
> Reporter: Guillaume Nodet
> Fix For: 1.1.0
>
> Attachments: SMX4KNL-169.patch
>
>
> This should allow hot fail-over with all bundles being already installed and
> ready to be started.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
