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

[Bartosz Baranowski (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-10280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595950#comment-13595950 ] 

Bartosz Baranowski commented on WFLY-10280:
-------------------------------------------

{quote}
Thread [ServerService Thread Pool -- 43] (Suspended (breakpoint at line 101 in ServiceName))	
	ServiceName.<init>(ServiceName, String) line: 101	
	ServiceName.of(ServiceName, String...) line: 92	
	ServiceName.of(String...) line: 70	
	ServiceName.parse(String) line: 482	
	ServiceNameFactory.parseServiceName(String) line: 46	
	OperationContextImpl.*getCapabilityServiceName*(String, Class<?>, PathAddress) line: 1672	
	ParallelBootOperationContext.*getCapabilityServiceName*(String, Class<?>) line: 394	
	*BinaryRequirementServiceNameFactory.getServiceName(OperationContext, String, String) line: 45*
	ClusteringCacheRequirement(DefaultableBinaryServiceNameFactoryProvider).getServiceName(OperationContext, String, String) line: 44	
	EJBRemotingConnectorClientMappingsEntryProviderService.configure(OperationContext) line: 76	
	EJB3RemoteServiceAdd.installRuntimeServices(OperationContext, ModelNode) line: 88	
	EJB3RemoteServiceAdd.performBoottime(OperationContext, ModelNode, ModelNode) line: 76	
	EJB3RemoteServiceAdd(AbstractBoottimeAddStepHandler).performBoottime(OperationContext, ModelNode, Resource) line: 144	
	EJB3RemoteServiceAdd(AbstractBoottimeAddStepHandler).performRuntime(OperationContext, ModelNode, Resource) line: 119	
	AbstractAddStepHandler$1.execute(OperationContext, ModelNode) line: 159	
	ParallelBootOperationContext(AbstractOperationContext).executeStep(AbstractOperationContext$Step) line: 999	
	ParallelBootOperationContext(AbstractOperationContext).processStages() line: 743	
	ParallelBootOperationContext(AbstractOperationContext).executeOperation() line: 467	
	ParallelBootOperationStepHandler$ParallelBootTask.run() line: 384	
	ContextClassLoaderSavingRunnable.run() line: 35	
	EnhancedQueueExecutor.safeRun(Runnable) line: 1985	
	EnhancedQueueExecutor$ThreadBody.doRunTask(Runnable) line: 1487	
	EnhancedQueueExecutor$ThreadBody.run() line: 1349	
	JBossThread(Thread).run() line: 748	
	JBossThread.run() line: 485	
{quote}

Which installs capability/service(?) "service org.wildfly.clustering.cache.registry-entry.ejb.client-mappings" later on, unless method name and vars are misleading? 


> 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: Bartosz Baranowski
>         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.
> 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)