Details

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

      Description

      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:

      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)
      

      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/

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  rachmato Richard Achmatowicz
                  Reporter:
                  mvinkler Michal Vinkler
                  Tester:
                  Michal Vinkler
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: