[jboss-jira] [JBoss JIRA] (WFLY-9923) EJBCLIENT000509: Unexpected exception processing EJB request: NPE during server graceful shutdown

[Richard Janík (JIRA)]

Richard Janík created WFLY-9923:
-----------------------------------

             Summary: EJBCLIENT000509: Unexpected exception processing EJB request: NPE during server graceful shutdown
                 Key: WFLY-9923
                 URL: https://issues.jboss.org/browse/WFLY-9923
             Project: WildFly
          Issue Type: Bug
          Components: Clustering, EJB
    Affects Versions: 12.0.0.Beta1
            Reporter: Richard Janík
            Assignee: David Lloyd


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:
{noformat}
[JBossINF] 05:27:23,973 WARN  [org.infinispan.transaction.impl.TransactionTable] (ServerService Thread Pool -- 81) ISPN000100: Stopping, but there are 0 local transactions and 28 remote transactions that did not finish in time.
[JBossINF] 05:27:23,974 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 81) WFLYCLINF0003: Stopped clusterbench-ee7.ear/clusterbench-ee7-ejb.jar cache from ejb container
[JBossINF] 05:27:23,989 ERROR [org.jboss.ejb.client.invocation] (default task-88) 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:400)
[JBossINF] 	at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:116)
[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$receiveMessage$2(RemoteConnectionChannel.java:361)
[JBossINF] 	at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926)
[JBossINF] 	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979)
[JBossINF] 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481)
[JBossINF] 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374)
[JBossINF] 	at java.lang.Thread.run(Thread.java:748)
{noformat}

Server log:
[ejbremote-shutdown-dist-sync-server1|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-ejb-ejbremote-shutdown-dist-sync-3owners/32/console-perf18/]
[ejbremote-shutdown-dist-sync-server4|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-ejb-ejbremote-shutdown-dist-sync-3owners/32/console-perf21/]



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