[jboss-jira] [JBoss JIRA] (WFLY-10280) can't enable stateful EJB passivation when EJB remote service is removed

[Ladislav Thon (JIRA)]

Ladislav Thon created WFLY-10280:
------------------------------------

             Summary: can't enable stateful EJB passivation when EJB remote service is removed
                 Key: WFLY-10280
                 URL: https://issues.jboss.org/browse/WFLY-10280
             Project: WildFly
          Issue Type: Bug
          Components: Clustering, EJB
    Affects Versions: 12.0.0.Final
            Reporter: Ladislav Thon
            Assignee: Paul Ferraro
         Attachments: tinyEjbPassivation.war

In WildFly Swarm, we don't have EJB remoting enabled by default, but would still like to be able to use stateful EJB passivation. We can't because of this bug.

Steps to reproduce:

{code}
unzip wildfly-12.0.0.Final.zip
cd wildfly-12.0.0.Final
cp tinyEjbPassivation.war standalone/deployments # any EJB deployment should do
./bin/jboss-cli.sh
embed-server --admin-only --std-out=echo --server-config=standalone-full.xml
/subsystem=ejb3:write-attribute(name=default-sfsb-cache,value=passivating)
/subsystem=ejb3/service=remote:remove
reload --start-mode=normal
{code}

What I do here is change the default SFSB cache to {{passivating}}, thereby enabling SFSB passivation, and also remove the {{remote}} service (which is what we do in WildFly Swarm by default).

When reloading the server to normal mode, deployment fails with a lot of errors, the main culprit seems to be the EJB client mappings registry:

{code}
17:16:37,216 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184:    New missing/unsatisfied dependencies:
      service jboss.deployment.unit."tinyEjbPassivation.war".HelloBean.bean-manager (unavailable) dependents: [service jboss.deployment.unit."tinyEjbPassivation.war".component.HelloBean.cache] 
      service jboss.deployment.unit."tinyEjbPassivation.war".component.HelloBean.START (unavailable) dependents: [service jboss.deployment.unit."tinyEjbPassivation.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."tinyEjbPassivation.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./tinyEjbPassivation, service jboss.deployment.unit."tinyEjbPassivation.war".WeldEndInitService] 
      service jboss.deployment.unit."tinyEjbPassivation.war".component.HelloBean.cache (unavailable) dependents: [service jboss.deployment.unit."tinyEjbPassivation.war".component.HelloBean.START] 
      service jboss.undertow.deployment.default-server.default-host./tinyEjbPassivation (unavailable) dependents: [service jboss.deployment.unit."tinyEjbPassivation.war".deploymentCompleteService] 
      service org.wildfly.clustering.cache.registry.ejb.client-mappings (unavailable) dependents: [service jboss.deployment.unit."tinyEjbPassivation.war".HelloBean.bean-manager] 
      service org.wildfly.clustering.cache.registry-entry.ejb.client-mappings (missing) dependents: [service org.wildfly.clustering.cache.registry.ejb.client-mappings] 
{code}



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)