Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-444

WFLYEJB0467: The request was rejected as the container is suspended during server shutdown

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Verified (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 7.0.0.DR6, 7.0.0.DR8, 7.0.0.ER2 (Beta)
    • Fix Version/s: 7.1.0.DR1
    • Component/s: Clustering, EJB
    • Labels:
      None

      Description

      Seen in our failover tests (scenario shutdown) for remote stateful EJBs
      Setup: 4 node cluster, one node at time is shutdown, while standalone clients keep calling the application.

      When server is shutting down (via cli command ":shutdown"), it logs the following error message for each client invocation during suspend phase:

      [JBossINF] [0m[0m12:36:39,319 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0211: Suspending server
      		 
      [JBossINF] [0m[0m12:36:39,323 INFO  [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.
      		 
      [JBossINF] [0m[31m12:36:39,346 ERROR [org.jboss.as.ejb3.invocation] (EJB default - 7) WFLYEJB0034: EJB Invocation failed on component RemoteStatefulSBImpl for method public abstract int org.jboss.test.clusterbench.common.ejb.CommonStatefulSB.getSerialAndIncrement(): org.jboss.as.ejb3.component.EJBComponentUnavailableException: WFLYEJB0467: The request was rejected as the container is suspended
      		 
      [JBossINF] 	at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:50)
      		 
      [JBossINF] 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
      		 
      [JBossINF] 	at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66)
      		 
      [JBossINF] 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
      		 
      [JBossINF] 	at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
      		 
      [JBossINF] 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
      		 
      [JBossINF] 	at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
      		 
      [JBossINF] 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
      		 
      [JBossINF] 	at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
      		 
      [JBossINF] 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
      		 
      [JBossINF] 	at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
      		 
      [JBossINF] 	at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:635)
      		 
      [JBossINF] 	at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61)
      		 
      [JBossINF] 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
      		 
      [JBossINF] 	at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
      		 
      [JBossINF] 	at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)
      		 
      [JBossINF] 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
      		 
      [JBossINF] 	at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
      		 
      [JBossINF] 	at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195)
      		 
      [JBossINF] 	at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:331)
      		 
      [JBossINF] 	at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:69)
      		 
      [JBossINF] 	at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:202)
      		 
      [JBossINF] 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      		 
      [JBossINF] 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      		 
      [JBossINF] 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      		 
      [JBossINF] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      		 
      [JBossINF] 	at java.lang.Thread.run(Thread.java:745)
      		 
      [JBossINF] 	at org.jboss.threads.JBossThread.run(JBossThread.java:320)

      Server log:
      http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-ejbremote-shutdown-dist-async/2/console-perf18/

        Gliffy Diagrams

          Attachments

            Issue Links

            cloned to

            Bug - A problem which impairs or prevents the functions of the product. WFLY-4939 WFLYEJB0467: The request was rejected as the container is suspended during server shutdown

            • Major - A request that should be considered seriously but is not a show stopper.
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. JBEAP-5628 (7.1.0) WFLYEJB0467: The request was rejected as the container is suspended during server shutdown

            • Major - A request that should be considered seriously but is not a show stopper.
            • Verified

              Activity

                People

                • Assignee:
                  rpelisse Romain Pelisse
                  Reporter:
                  mvinkler Michal Vinkler
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  9 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - 3 days
                    3d
                    Remaining:
                    Remaining Estimate - 3 days
                    3d
                    Logged:
                    Time Spent - Not Specified
                    Not Specified