-
Bug
-
Resolution: Done
-
Minor
-
8.0 Update 1
-
False
-
None
-
False
-
-
-
-
-
-
?
-
- Dont change cache container name. Keep it as ejb.
-
-
I wrote up [2] for the distributable-ejb for docs based on [1] , but it looks like the ejb remote service still requires ejb.
20:43:51,230 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=ejb3/service=remote' are not available: org.wildfly.clustering.infinispan.cache-container.ejb; Possible registration points for this capability: /subsystem=infinispan/cache-container=*/local-cache=* /subsystem=infinispan/cache-container=*/invalidation-cache=* /subsystem=infinispan/cache-container=*/replicated-cache=* /subsystem=infinispan/cache-container=*/distributed-cache=* /subsystem=infinispan/cache-container=*/scattered-cache=* /subsystem=infinispan/cache-container=* 20:43:51,237 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. - Server configuration file in use: standalone-ha.xml
./bin/standalone.sh -c standalone-full-ha.xml
The customer renamed all "ejb" to "ejb2" , but the ejb3 remote service still shows it defaults to ejb if cluster is removed and the error above shows this service is looking for a cache-container named ejb:
/subsystem=ejb3/service=remote:read-attribute(name=cluster)
{
"outcome" => "success",
"result" => "ejb"
}
- clones
-
-
- Resolved
-
