0 Replies Latest reply on Feb 17, 2014 3:44 AM by Stephan Windmüller

    After 46 hours of stress testing: No EJB receiver available for handling [...] combination

    Stephan Windmüller Newbie

      Hello,

       

      I am trying to stress-test our Jboss (7.1.3) server. This works well for a long time (last try: 46 hours) in which I perform random queries in up to 16 threads on the EJBs using the EJBClientContext.

       

      However, after about 100,000 queries, suddenly the connection is not possible anymore and I get an exception:

       

      java.lang.IllegalStateException: No EJB receiver available for handling [appName:my-app,modulename:backend,distinctname:] combination

              at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:530)

              at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:84)

              at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:175)

              at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)

              at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)

              at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)

              at sun.proxy.$Proxy34.myMethod(Unknown Source)

       

      There are no errors in the Jboss logs at this point. Restarting Jboss seems to fix the problem, but this is of course no solution.

       

      So my question is: Which part is responsible for the sudden connection fail? I noticed something like

       

      final int MAX_RECONNECT_ATTEMPTS = 65535;

       

      in ConfigBasedEJBClientContextSelector, could this have to do with my problem?