WildFly Infinispan Subsystem Configuration: Difference between revisions
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
<font color=red> | <font color=red> | ||
'''TODO''': Did not work - I only started clustering if I deployed a distributable servlet. Investigate why. Then link from [[]] to the final explanation header. | '''TODO''': Did not work - I only started clustering if I deployed a distributable servlet. Investigate why. Then link from [[WildFly Clustering without Multicast#Why_Doesn.27t_the_Cluster_Form.3F]] to the final explanation header. | ||
If the servers are not specifically configured to eagerly start the caches, JGroups channels are not initialized at boot, so the cluster does not form, unless an application specifically requires clustering. | If the servers are not specifically configured to eagerly start the caches, JGroups channels are not initialized at boot, so the cluster does not form, unless an application specifically requires clustering. | ||
Revision as of 09:15, 24 February 2016
Internal
Organizatorium
Caches Do Not Start at Boot Even if Declared Eager
TODO: Did not work - I only started clustering if I deployed a distributable servlet. Investigate why. Then link from WildFly Clustering without Multicast#Why_Doesn.27t_the_Cluster_Form.3F to the final explanation header.
If the servers are not specifically configured to eagerly start the caches, JGroups channels are not initialized at boot, so the cluster does not form, unless an application specifically requires clustering.
In order to eagerly start the cache:
/profile=ha/subsystem=infinispan/cache-container=web:write-attribute(name=start,value=eager)