[jboss-jira] [JBoss JIRA] (WFLY-5785) EJB lookup fails with "No cluster context available" in failover tests

[Paul Ferraro (JIRA)]

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

Paul Ferraro commented on WFLY-5785:
------------------------------------

I'll take this over with a better fix.

> EJB lookup fails with "No cluster context available" in failover tests
> ----------------------------------------------------------------------
>
>                 Key: WFLY-5785
>                 URL: https://issues.jboss.org/browse/WFLY-5785
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 10.0.0.CR5
>            Reporter: Michal Vinkler
>            Assignee: Dominik Pospisil
>
> Seen in our failover tests for remote stateful EJBs - scenarios:
> ejb-ejbremote-shutdown-dist-async
> ejb-ejbremote-shutdown-dist-sync
> ejb-ejbremote-undeploy-dist-async
> After failing a node, occasionally EJB lookup starts failing - client starts logging these error messages:
> {code}
> 2015/12/03 04:46:47:078 EST [ERROR][Runner - 9] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <java.lang.IllegalStateException: EJBCLIENT000029: No cluster context available for cluster named ejb>
>         java.lang.IllegalStateException: EJBCLIENT000029: No cluster context available for cluster named ejb
>         at org.jboss.ejb.client.EJBClientContext.requireClusterEJBReceiverContext(EJBClientContext.java:1063)
>         at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:84)
>         at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
>         at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
>         at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
>         at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
>         at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
>         at com.sun.proxy.$Proxy2.getSerialAndIncrement(Unknown Source)
>         at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:84)
>         at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
>         at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
>         at java.lang.Thread.run(Thread.java:745)
> {code}
> It stops logging these messages only after the failed node is restarted and joins the cluster again.
> Link (this job was configured to use only 100 sessions in order to keep the log size small)
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/mvinkler_eap-7x-failover-ejb-ejbremote-shutdown-dist-async/1/console-perf17/



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)