]
Paul Ferraro updated WFLY-5752:
-------------------------------
Summary: SFSB deployment fails when passivation-store is configured with custom
cache-container (was: Can't rename the "ejb" cache container)
SFSB deployment fails when passivation-store is configured with
custom cache-container
--------------------------------------------------------------------------------------
Key: WFLY-5752
URL:
https://issues.jboss.org/browse/WFLY-5752
Project: WildFly
Issue Type: Bug
Components: Clustering, EJB
Reporter: Ladislav Thon
Assignee: Paul Ferraro
Priority: Blocker
Attachments: tinyRemoteEjb-server-ee7.jar
When I rename the {{ejb}} cache container, deploying a simple app that contains an EJB
ends with a horrible error message. This is a blocker, because renaming a cache container
is required for a 2clusters scenario (standalone client invoking a remote EJB in cluster
A, that EJB in turns invokes a remote EJB in cluster B, and forwards the response to the
original client).
More details:
1. build current WildFly master and {{unzip
.../wildfly/build/target/wildfly-10.0.0.CR5-SNAPSHOT.zip}}
2. {{cp tinyRemoteEjb-server-ee7.jar
wildfly-10.0.0.CR5-SNAPSHOT/standalone/deployments/}} # the JAR is attached
3. change the
{{wildfly-10.0.0.CR5-SNAPSHOT/standalone/configuration/standalone-full-ha.xml}} file like
this:
{code}
<!-- in the "ejb3" subsystem -->
<passivation-store name="infinispan" cache-container="ejb2"
max-size="10000"/>
<remote cluster="ejb2" connector-ref="http-remoting-connector"
thread-pool-name="default"/>
<!-- in the "infinispan" subsystem -->
<cache-container name="ejb2" ...>
{code}
4. {{./wildfly-10.0.0.CR5-SNAPSHOT/bin/standalone.sh -c standalone-full-ha.xml}}
This leads to:
{code}
14:11:22,473 ERROR [org.jboss.as.controller.management-operation] (Controller Boot
Thread) WFLYCTL0013: Operation ("deploy") failed - address:
([("deployment" => "tinyRemoteEjb-server-ee7.jar")]) - failure
description: {"WFLYCTL0288: One or more services were unable to start due to one or
more indirect dependencies not being available." => {
"Services that were unable to start:" => [
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".CdiValidatorFactoryService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".WeldStartService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.CREATE",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.JndiBindingsService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.START",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.VIEW.\"cz.ladicek.tinyRemoteEjb.server.MyBean\".REMOTE",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.WeldInstantiator",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".component.MyBeanImpl.WeldInterceptorBindingsService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".deploymentCompleteService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".jndiDependencyService",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".moduleDeploymentRuntimeInformation",
"jboss.deployment.unit.\"tinyRemoteEjb-server-ee7.jar\".moduleDeploymentRuntimeInformationStart",
"jboss.naming.context.java.app.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.MyBeanImpl",
"jboss.naming.context.java.app.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\"",
"jboss.naming.context.java.global.tinyRemoteEjb-server-ee7.MyBeanImpl",
"jboss.naming.context.java.global.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\"",
"jboss.naming.context.java.module.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.MyBeanImpl",
"jboss.naming.context.java.module.tinyRemoteEjb-server-ee7.tinyRemoteEjb-server-ee7.\"MyBeanImpl!cz.ladicek.tinyRemoteEjb.server.MyBean\""
],
"Services that may be the cause:" =>
["jboss.clustering.registry.ejb2.client-mappings"]
}}
14:11:22,476 ERROR [org.jboss.as.controller.management-operation] (Controller Boot
Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "ejb3"),
("service" => "remote")
]) - failure description: {"WFLYCTL0180: Services with missing/unavailable
dependencies" => ["jboss.ejb.remoting.connector.client-mappings.installer is
missing [jboss.clustering.registry.ejb2.client-mappings]"]}
{code}
This works perfectly fine in 10.0.0.CR4, so I did a {{git bisect}} and traced the problem
to this commit:
https://github.com/wildfly/wildfly/commit/232dff042f The error message
mentions that an {{...ejb2.client-mappings}} service is missing, which is consistent with
the commit message (also mentions client mappings).