-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
7.0.5.GA, 7.0.6.GA, 7.0.7.GA, 7.0.8.GA, 7.0.9.GA
A client is successfully getting all cluster information, but the Attachment containing the WeakAffinity information contain only 'None' instead of 'cluster', so the ClusterNodeSelector is not being used.
This is fixed in JBEAP-14228, but only for a default configuration where the cluster name is ejb.
In case the cluster is renamed with the following configuration to ejb-cluster-2, the ClusterNodeSelector is still not being used:
:
<subsystem xmlns="urn:jboss:domain:ejb3:4.0">
:
<passivation-stores>
<passivation-store name="infinispan" cache-container="ejb-cluster-2" max-size="10000"/>
</passivation-stores>
:
<remote cluster="ejb-cluster-2" connector-ref="http-remoting-connector" thread-pool-name="default"/>
:
</subsystem>
:
<subsystem xmlns="urn:jboss:domain:infinispan:4.0">
:
<cache-container name="ejb-cluster-2" aliases="sfsb" default-cache="dist" module="org.wildfly.clustering.ejb.infinispan">
<transport lock-timeout="60000"/>
<distributed-cache name="dist" mode="ASYNC" l1-lifespan="0" owners="2">
<locking isolation="REPEATABLE_READ"/>
<transaction mode="BATCH"/>
<file-store/>
</distributed-cache>
</cache-container>
:
</subsystem>
:
- relates to
-
-
- Closed
-
- links to