WildFly Infinispan Subsystem Configuration: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
* [[WildFly Infinispan Subsystem#Subjects|WildFly Infinispan Subsystem]] | * [[WildFly Infinispan Subsystem#Subjects|WildFly Infinispan Subsystem]] | ||
=Organizatorium= | |||
==Caches Do Not Start at Boot Even if Declared Eager== | |||
<font color=red> | |||
'''TODO''': Did not work - I only started clustering if I deployed a distributable servlet. Investigate why. | |||
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: | |||
<pre> | |||
/profile=ha/subsystem=infinispan/cache-container=web:write-attribute(name=start,value=eager) | |||
</pre> | |||
</font> | |||
Revision as of 09:13, 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.
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)