In support ticket 01808463 [1] the customer reports that renaming the cache-container "ejb" to "ejb-<appname>" and renaming the reference in the "cluster-passivation-store" - which worked in EAP 6.4.x installations - fails on EAP 7.0.4.

Apparently the configuration for adding additional cache containers has changed in Wildfly 10.0.0, introducing a new "cluster" element to the EJB3 subsystem's remote element (which configures the EJB subsystem's remoting connector service) so that the name specified will be used in topology updates returned to the client from the cluster, along with the client mappings.

This is described in WFLY-3290 [2]. The relevant Wildfly documentation seems to be [3] but this does not mention the changes in WFLY-3290.

Similarly, EAP documentation pertaining to cache configuration [4] seems to be missing any reference to the required element(s).

[1] https://c.na7.visual.force.com/apex/Case_View?sbstr=01808463
[2] https://issues.jboss.org/browse/WFLY-3290
[3] https://docs.jboss.org/author/display/WFLY10/EJB3+subsystem+configuration+guide
[4] https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/html/configuration_guide/configuring_high_availability#infinispan