[ 
https://issues.apache.org/activemq/browse/SMX4KNL-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48771#action_48771
 ] 

Jamie Goodyear commented on SMX4KNL-169:
----------------------------------------


h6. JMX port bind exception.

When smx creates instances on a single host each instance reuses the 
'servicemix' startup script of the parent. The parent servicemix start script 
just appends the jmx remote jvm argument to command line. We can indicate when 
we want org.apache.servicemix.kernel.management-1.1.0-SNAPSHOT.jar loaded via 
the $SMX_HOME/etc/startup.properties file, allowing the management components 
to not be loaded until the SMX run level is achieved.

* In the case where the management component is above the current start level 
no bind error will occur.
** management.jar=30   lock.level=1
* In the case where the management component is below the start level we will 
see bind exceptions.
** management.jar=30   lock.level=50

h5. Possible solutions.

One solution would be to alter each instance of SMX to have its own JMX port, 
thereby removing contention for the JMX port (much the same way that each 
instance has its own port upon creation).

Another solution would be to link startup of the management components to which 
instance is currently master in the deployment (if the instance has the lock 
then it may load the management jar). This should allow jmx remote to remain on 
one default port. 

Is there any preference to how this should be addressed?
  

> 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.

Reply via email to