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

EJBCLIENT000509: Unexpected exception processing EJB request: NPE during server graceful shutdown

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 7.1.0.CR3, 7.1.0.CR4
    • Clustering, EJB
    • None
    • Regression

      Seen in our clustering failover tests for remote stateful EJBs.
      Setup: 4 node cluster, one node at the time is shut down gracefully, while 2000 standalone clients keep calling the application.

      During the graceful shutdown, 2 servers logged this error message right after stopping the deployment:

      [JBossINF] �[0m�[0m14:27:53,722 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 81) ISPN000030: Passivated 1938 entries in 468 milliseconds
      [JBossINF] �[0m�[33m14:27:53,734 WARN  [org.infinispan.transaction.impl.TransactionTable] (ServerService Thread Pool -- 81) ISPN000100: Stopping, but there are 0 local transactions and 53 remote transactions that did not finish in time.
      [JBossINF] �[0m�[0m14:27:53,736 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 81) WFLYCLINF0003: Stopped clusterbench-ee7.ear/clusterbench-ee7-ejb.jar cache from ejb container
      [JBossINF] �[0m�[31m14:27:53,763 ERROR [org.jboss.ejb.client.invocation] (default task-34) EJBCLIENT000509: Unexpected exception processing EJB request: java.lang.NullPointerException
      [JBossINF] 	at org.jboss.as.ejb3.deployment.DeploymentRepository.getStartedModules(DeploymentRepository.java:202)
      [JBossINF] 	at org.jboss.as.ejb3.remote.AssociationImpl.findEJB(AssociationImpl.java:393)
      [JBossINF] 	at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:115)
      [JBossINF] 	at org.jboss.ejb.protocol.remote.EJBServerChannel$ReceiverImpl.handleInvocationRequest(EJBServerChannel.java:450)
      [JBossINF] 	at org.jboss.ejb.protocol.remote.EJBServerChannel$ReceiverImpl.handleMessage(EJBServerChannel.java:188)
      [JBossINF] 	at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
      [JBossINF] 	at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926)
      [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:748)
      [JBossINF] 
      

      This error was observed nearly in all graceful shutdown scenarios.

      Server log:
      http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-ejb-ejbremote-shutdown-dist-async/34/console-perf18/

            rpelisse@redhat.com Romain Pelisse
            mvinkler1@redhat.com Michal Vinkler
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: