-
Bug
-
Resolution: Obsolete
-
Major
-
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 was introduced with the change of WFLY-6316, JBEAP-4928
- is caused by
-
JBEAP-4928 (7.0.x) Deploying @Stateless EJB causes default ejb cache to start unnecessarily
- Verified
- is related to
-
JBEAP-14311 [GSS] (7.0.z) Client loadbalancing broken, ClusterNodeSelector not used when cluster name is not 'ejb'
- Closed
- links to