0 Replies Latest reply on May 20, 2014 10:34 AM by bibhunayak

    not able to access ejb3 from axis2 client

    bibhunayak
    bibhunayak May 20, 2014 10:34 AM

      Hi ,

      I am trying to access ejb3 deployed on one JBossAS 7 instance(Destination Server) from another JBossAS 7 instance(Client Server).EJB is deployed in destination server as WAR and the client is packaged in AXIS2.war.I have created outbound connection on client. Successful handshake is also happening. While firing request from SOAPUI I am getting below exception.

       

      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

         <soapenv:Body>

            <soapenv:Fault>

               <faultcode>soapenv:Server</faultcode>

               <faultstring>No EJB receiver available for handling [appName:,modulename:lms,distinctname:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@1f4d6623</faultstring>

               <detail>

                  <Exception>org.apache.axis2.AxisFault: No EJB receiver available for handling [appName:,modulename:lms,distinctname:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@1f4d6623

      at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)

        at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)

      at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)

      at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)

      at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)

      at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)

      at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)

      at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)

      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)

      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)

      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)

      at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)

      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)

      at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)

      at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)

      at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)

      at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)

      at java.lang.Thread.run(Thread.java:662)

      Caused by: java.lang.IllegalStateException: No EJB receiver available for handling [appName:,modulename:lms,distinctname:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@1f4d6623

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

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

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

      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)

        ... 20 more</Exception>

               </detail>

            </soapenv:Fault>

         </soapenv:Body>

      </soapenv:Envelope>

       

       

      Please help me to resolve the issue.

      Thanks,

      Bibhu