0 Replies Latest reply on Jul 11, 2018 7:36 AM by chamini prashakthi

    Exception in thread "main" java.lang.IllegalStateException: No EJB receiver available for handling

    chamini prashakthi Newbie

      My application use jvboss 7.1 and session bean 3.1 here.Also mu bean lookup is like this:

       

      private static String getLookupName() {
      /*The app name is the EAR name of the deployed EJB without .ear 
      suffix. Since we haven't deployed the application as a .ear, the app 
      name for us will be an empty string */
      String appName = "";
      
      
      /* The module name is the JAR name of the deployed EJB without the 
      .jar suffix.*/
      String moduleName = "EmployeeModule";
      
      
      /* AS7 allows each deployment to have an (optional) distinct name. 
      This can be an empty string if distinct name is not specified.*/
      String distinctName = "";
      
      
      // The EJB bean implementation class name
      String beanName = EmployeeBean.class.getSimpleName();
      
      
      // Fully qualified remote interface name
      final String interfaceName = EmployeeBeanInterface.class.getName();
      
      
      // Create a look up string name
      String name = "ejb:" + appName + "/" + moduleName + "/" + 
      distinctName + "/" + beanName + "!" + interfaceName;
      return name;
      }
      

      But it shows an error log as this.

      I can't figure out any error here.

       

      Jul 9, 2018 3:08:08 PM org.jboss.ejb.client.EJBClient <clinit>
      INFO: JBoss EJB Client version 1.0.5.Final
      Jul 9, 2018 3:08:08 PM org.xnio.Xnio <clinit>
      INFO: XNIO Version 3.0.3.GA
      Jul 9, 2018 3:08:08 PM org.xnio.nio.NioXnio <clinit>
      INFO: XNIO NIO Implementation Version 3.0.3.GA
      Jul 9, 2018 3:08:08 PM org.jboss.remoting3.EndpointImpl <clinit>
      INFO: JBoss Remoting version 3.2.3.GA
      Jul 9, 2018 3:08:08 PM org.jboss.ejb.client.remoting.VersionReceiver handleMessage
      INFO: Received server version 1 and marshalling strategies [river]
      Jul 9, 2018 3:08:08 PM org.jboss.ejb.client.remoting.ChannelAssociation$ResponseReceiver handleMessage
      WARN: Unsupported message received with header 0xffffffff
      Jul 9, 2018 3:08:08 PM org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver associate
      INFO: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1e152c5, receiver=Remoting connection EJB receiver [connection=Remoting connection <872380>,channel=jboss.ejb,nodename=cwlk-chaminip]} on channel Channel ID 8aaa4baf (outbound) of Remoting connection 001fc2fb to localhost/127.0.0.1:4447
      Jul 9, 2018 3:08:13 PM org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver associate
      INFO: Initial module availability report for Remoting connection EJB receiver [connection=Remoting connection <872380>,channel=jboss.ejb,nodename=cwlk-chaminip] wasn't received during the receiver context association
      Exception in thread "main" java.lang.IllegalStateException: No EJB receiver available for handling [appName:,modulename:EmployeeModule,distinctname:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@10f6d3
      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)
      at $Proxy0.save(Unknown Source)
      at com.employee.client.EmployeeApplicationClient.main(EmployeeApplicationClient.java:26)