You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Gert Vanthienen (Updated) (JIRA)" <ji...@apache.org> on 2011/12/06 10:17:40 UTC
[jira] [Updated] (SMX4NMR-195) Dynamically enable/disable cluster
engine when ConnectionFactory available in registry
[ https://issues.apache.org/jira/browse/SMX4NMR-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen updated SMX4NMR-195:
------------------------------------
Affects Version/s: (was: 1.2.0)
1.6.0
Deferring to NMR 1.6.0
> Dynamically enable/disable cluster engine when ConnectionFactory available in registry
> --------------------------------------------------------------------------------------
>
> Key: SMX4NMR-195
> URL: https://issues.apache.org/jira/browse/SMX4NMR-195
> Project: ServiceMix NMR
> Issue Type: Improvement
> Affects Versions: 1.6.0
> Reporter: Gert Vanthienen
> Fix For: 1.5.0
>
>
> Currently, the Cluster engine is configured with a Blueprint proxy to the ConnectionFactory that's available in the OSGi Service Registry. This way, the Cluster Engine isn't aware of changes in the registry (e.g. the ConnectionFactory is being removed or a new one is registered).
> We should improve the engine to dynamically enable/disable clustering depending on the availability of a suitable ConnectionFactory.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira