1 Reply Latest reply on Oct 25, 2014 10:12 AM by Mitesh Manani

    migrating Jboss EAP 4.2 to Jboss EAP 6

    amirtharaj chinnaraj Newbie

      Hi ,


        we are trying to migrate our existing application which runs in EAP 4.2 to EAP 6. we did every thing as mentioned in Jboss Documentaion and it runs fine in DEV and SQA region. However its failing in production.


      Our application uses Tomcat 6 ,which will act as EJB client and communicates with the Jboss EAP 6 to lookup the EJB, As soon as load increasese we are getting following error in the tomcat. if the load is less everything this fine.


      035D24792-9434-A562-F9F5-05B6E4D255321021021402java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:22000-XXXXX, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@58b5319d1

      though i searched several forms and found my Initial context is also fine , which has all the required parameters as sown below .

            jndiProps.put(Context.INITIAL_CONTEXT_FACTORY, System.getProperty(INITIAL).trim());

            jndiProps.put(Context.URL_PKG_PREFIXES, System.getProperty(PKG_PREFIXES).trim());

            jndiProps.put(Context.PROVIDER_URL, System.getProperty(URL).trim());

            jndiProps.put("jboss.naming.client.ejb.context", Boolean.valueOf(System.getProperty(CLIENT_CONTEXT).trim()).booleanValue());

            jndiProps.put(Context.SECURITY_PRINCIPAL, System.getProperty(USER).trim());

            jndiProps.put(Context.SECURITY_CREDENTIALS, System.getProperty(PASSWORD).trim());


      Also we took heap Dump to analyse the root cause. the Dump shows the objects of the type org.jboss.remoting3.remote.RemoteConnectionProvider$1 occupies 90% of Heap.



      Jboss server is stable only the remote client are causing issues. Also we find few of them faced same kind of problem and  reported as jBoss Bug.



      we just want to know are thier any fix for this issue ,or if some one having any solutions , workaround for this ..Please let us know