[jboss-jira] [JBoss JIRA] (WFLY-12488) WFLYEJB0467: The request was rejected as the container is suspended

[James Perkins (Jira)]

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

James Perkins commented on WFLY-12488:
--------------------------------------

I'm not an EJB expert, but I think more logs would be needed to see where this is happening. It looks like the server may still be suspended so before the server is fully started there is an attempt to do an EJB lookup. Due to this I'm reducing this from a blocker as it's likely not a server error.

> WFLYEJB0467: The request was rejected as the container is suspended
> -------------------------------------------------------------------
>
>                 Key: WFLY-12488
>                 URL: https://issues.jboss.org/browse/WFLY-12488
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 17.0.1.Final
>         Environment: Windows 10
> Wildfly 17
>            Reporter: Yugamani K
>            Assignee: Cheng Fang
>            Priority: Major
>
> Unable to lookup EJB after it is being registered with JNDI.
> EJB is coming up, few mins after the server startup.
> {code}
> Caused by: javax.naming.NamingException: WFLYNAM0062: Failed to lookup ncp/ncputils/NumberGeneratorBean!com.ndfs.common.numbergenerator.ejb.NumberGeneratorRemote [Root exception is java.lang.RuntimeException: org.jboss.as.ejb3.component.EJBComponentUnavailableException: WFLYEJB0467: The request was rejected as the container is suspended]
> 	at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:159)
> 	at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83)
> 	at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
> 	at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
> 	at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
> 	at org.wildfly.naming.client.remote.RemoteServerTransport.handleLookup(RemoteServerTransport.java:185)
> 	at org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:106)
> 	at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
> 	at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:975)
> 	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> 	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> 	at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.RuntimeException: org.jboss.as.ejb3.component.EJBComponentUnavailableException: WFLYEJB0467: The request was rejected as the container is suspended
> 	at org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor$2$1.getReference(EjbJndiBindingsDeploymentUnitProcessor.java:253)
> 	at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:143)
> 	... 13 more
> Caused by: org.jboss.as.ejb3.component.EJBComponentUnavailableException: WFLYEJB0467: The request was rejected as the container is suspended
> 	at org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor$2$1.getReference(EjbJndiBindingsDeploymentUnitProcessor.java:245)
> 	... 14 more
> {code}



--
This message was sent by Atlassian Jira
(v7.13.5#713005)