WildFly Infinispan Subsystem Configuration: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
* [[WildFly Infinispan HTTP Session Replication Configuration]] | * [[WildFly Infinispan HTTP Session Replication Configuration]] | ||
=Overview= | |||
<blockquote style="background-color: Gold; border: solid thin Goldenrod;"> | |||
:<br>This section refers to configuring the ''internal'' WildFly caches. For details on how to setup a JDG cluster, see [[Infinispan Configuration]].<br><br> | |||
</blockquote> | |||
=Organizatorium= | =Organizatorium= | ||
Revision as of 00:13, 1 June 2016
Internal
Subjects
Overview
This section refers to configuring the internal WildFly caches. For details on how to setup a JDG cluster, see Infinispan Configuration.
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)