[jboss-jira] [JBoss JIRA] (AS7-3156) Cannot add clustered caches to a cache container started without a transport

[ https://issues.jboss.org/browse/AS7-3156?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz edited comment on AS7-3156 at 1/11/12 6:40 PM: ------------------------------------------------------------------- Just for the record, a short summary of how the mechanism works (my understanding) at the moment to include or not include a transport: {noformat} - CacheContainerAdd.performRuntime(): - creates TransportConfig and populates from <transport/> element in <cache-container/> element - creates EmbeddedCacheManagerDependencies (mbean server, listener executor, eviction executor, replication queue executor, transport configuration) and populates the injection points - creates EmbeddedCacheManagerService(name, defaultCache, dependencies) and adds an OPTIONAL dep on ChannelService(containerName) and starts ON_DEMAND - creates ChannelService(containerName), adds an alias TransportService(name) and installs it in mode NEVER Thus, the EmbeddedCacheManagerService dependency on TransportService is OPTIONAL, and this its presence or absence will not affect its start up. Also, ChannelService (alias TransportService) is installed and configured, but not started unless another service modifies its NEVER state back to ON_DEMAND. - EmbeddedCacheManagerService.start(): - takes in EmbeddedCacheManagerDependencies populated - uses Dependencies to configure GlobalConfigurationBuilder with injection poingts - the EmbeddedCacheManager is only configured to use a transport (by configuring TransportConfigurationBuilder) if ChannelService(name) is UP as a service when start() is called. Thus, the EmbeddedCacheManager will only be ISPN-configured to use a transport if some service has set the start mode of its ChannelService to ON_DEMAND *after* it is installed and *before* it starts. - CacheAdd.performRuntime(): - populates ConfigurationBuilder instance with cache configuration from ModelNode - creates CacheConfigurationService which holds ConfigurationBuilder and CachConfigurationDependencies (container, tm, tsr) - creates CacheService depending on CacheConfigurationService and CacheDependencies (container, recoveryReg) - if cache is clustered, adds dependency on TransportService(containerName) and sets the TransportService(containerName) start mode to ON_DEMAND - the CacheService is then installed Thus, installing a clustered cache "activates" the ChannelService of its container, and so triggers the EmbeddedCacheManagerService to configure a transport for its EmbededCacheManager instance. But this only has effect if this happens before the EmbeddedCacheManagerService is started (by HotRod or any other service which requests the start of a cache container directly). - CacheConfigurationService.start(): - add the injections from the tm and tsr to the ConfigurationBuilder - build the Configuration - define the configuration in the cache container - CacheService.start(): - get the cache instance from the container - add the XARecoveryRegistry for the container to the system wide recovery registry Thus, if a clustered cache is installed before the EmbeddedCacheManagerService is started, the ChannelService start mode will have been set to ON_DEMAND, and both the EmbeddedCacheManagerService and the CacheService will have a dependency on the ChannelService, which means that it will be started before the EmbeddedCacheManagerService is started. When EmbeddedCacheManagerService is started, it will find that the ChannelService is up, and it will then configure the EmbeddedCacheManager to use the available transport. This will not work if a component (e.g. perhaps HotRod) starts up a cache container and the creates a clustered cache in that container. {noformat} was (Author: rachmato): Just for the record, a short summary of how the mechanism works at the moment to include or not include a transport: {noformat} - CacheContainerAdd.performRuntime(): - creates TransportConfig and populates from <transport/> element in <cache-container/> element - creates EmbeddedCacheManagerDependencies (mbean server, listener executor, eviction executor, replication queue executor, transport configuration) and populates the injection points - creates EmbeddedCacheManagerService(name, defaultCache, dependencies) and adds an OPTIONAL dep on ChannelService(containerName) and starts ON_DEMAND - creates ChannelService(containerName), adds an alias TransportService(name) and installs it in mode NEVER Thus, the EmbeddedCacheManagerService dependency on TransportService is OPTIONAL, and this its presence or absence will not affect its start up. Also, ChannelService (alias TransportService) is installed and configured, but not started unless another service modifies its NEVER state back to ON_DEMAND. - EmbeddedCacheManagerService.start(): - takes in EmbeddedCacheManagerDependencies populated - uses Dependencies to configure GlobalConfigurationBuilder with injection poingts - the EmbeddedCacheManager is only configured to use a transport (by configuring TransportConfigurationBuilder) if ChannelService(name) is UP as a service when start() is called. Thus, the EmbeddedCacheManager will only be ISPN-configured to use a transport if some service has set the start mode of its ChannelService to ON_DEMAND *after* it is installed and *before* it starts. - CacheAdd.performRuntime(): - populates ConfigurationBuilder instance with cache configuration from ModelNode - creates CacheConfigurationService which holds ConfigurationBuilder and CachConfigurationDependencies (container, tm, tsr) - creates CacheService depending on CacheConfigurationService and CacheDependencies (container, recoveryReg) - if cache is clustered, adds dependency on TransportService(containerName) and sets the TransportService(containerName) start mode to ON_DEMAND - the CacheService is then installed Thus, installing a clustered cache "activates" the ChannelService of its container, and so triggers the EmbeddedCacheManagerService to configure a transport for its EmbededCacheManager instance. But this only has effect if this happens before the EmbeddedCacheManagerService is started (by HotRod or any other service which requests the start of a cache container directly). - CacheConfigurationService.start(): - add the injections from the tm and tsr to the ConfigurationBuilder - build the Configuration - define the configuration in the cache container - CacheService.start(): - get the cache instance from the container - add the XARecoveryRegistry for the container to the system wide recovery registry Thus, if a clustered cache is installed before the EmbeddedCacheManagerService is started, the ChannelService start mode will have been set to ON_DEMAND, and both the EmbeddedCacheManagerService and the CacheService will have a dependency on the ChannelService, which means that it will be started before the EmbeddedCacheManagerService is started. When EmbeddedCacheManagerService is started, it will find that the ChannelService is up, and it will then configure the EmbeddedCacheManager to use the available transport. This will not work if a component (e.g. perhaps HotRod) starts up a cache container and the creates a clustered cache in that container. {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira