Invoking EJB from standalone java client in JBoss7

[Bhavesh Sangwan]

Hi there ! I'm new to ejb. Using Eclipse and Jboss server. I've deployed an EJB and now want to invoke it using a standalone java program. I know that Eclipse and JBoss do some job to bind JNDI names. I just want to know that how to lookup EJB by which JNDI binding out of 6 options available (shown in deployment console) there.

Here I'm dropping all my java code and server/console logs please help...

LibrarySessionBeanRemote

package com.bhavesh.ejb;

import java.util.List;
import javax.ejb.Remote;
 
@Remote
public interface LibrarySessionBeanRemote {
 
    void addBook(String bookName);
 
    List getBooks();
    
}

LibrarySessionBean

package com.bhavesh.ejb;

import java.util.ArrayList;
import java.util.List;
import javax.ejb.Stateless;
 
@Stateless
public class LibrarySessionBean implements LibrarySessionBeanRemote {
    
    List<String> bookShelf;    
    
    public LibrarySessionBean(){
       bookShelf = new ArrayList<String>();
    }
    
    public void addBook(String bookName) {
        bookShelf.add(bookName);
    }    
 
    public List<String> getBooks() {
        return bookShelf;
    }
}

jndi.properties

java.naming.factory.initial=org.jboss.naming.remote.client.InitialContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java.naming.provider.url=remote://localhost:4447

jboss-ejb-client.properties

endpoint.name=client-endpoint
remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
remote.connections=default
remote.connection.default.host=localhost:8282
remote.connection.default.port = 4447
remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false

EJBTester

package com.bhavesh.client;

import com.bhavesh.ejb.LibrarySessionBeanRemote;
import java.io.BufferedReader;
import java.io.FileInputStream;
import java.io.IOException;
import java.io.InputStreamReader;
import java.util.List;
import java.util.Properties;
import javax.naming.InitialContext;
import javax.naming.NamingException;
 
 
public class EJBTester {
 
   BufferedReader brConsoleReader = null; 
   Properties props;
   InitialContext ctx;
   {
      props = new Properties();
      try {
      props.load(new FileInputStream("jndi.properties"));
      } catch (IOException ex) {
      ex.printStackTrace();
      }
      try {
      ctx = new InitialContext(props);            
      } catch (NamingException ex) {
      ex.printStackTrace();
      }
      brConsoleReader = 
      new BufferedReader(new InputStreamReader(System.in));
   }
   public static void main(String[] args) {
 
      EJBTester ejbTester = new EJBTester();
 
      ejbTester.testStatelessEjb();
   }
   private void showGUI(){
      System.out.println("**********************");
      System.out.println("Welcome to Book Store");
      System.out.println("**********************");
      System.out.print("Options \n1. Add Book\n2. Exit \nEnter Choice: ");
   }
   private void testStatelessEjb(){
      try {
         int choice = 1; 
         LibrarySessionBeanRemote libraryBean = 
         (LibrarySessionBeanRemote)ctx.lookup("java:module/LibrarySessionBean!com.bhavesh.ejb.LibrarySessionBeanRemote");
         while (choice != 2) {
            String bookName;
            showGUI();
            String strChoice = brConsoleReader.readLine();
            choice = Integer.parseInt(strChoice);
            if (choice == 1) {
               System.out.print("Enter book name: ");
               bookName = brConsoleReader.readLine();                    
               libraryBean.addBook(bookName);          
            }else if (choice == 2) {
               break;
            }
         }
         List<String> booksList = libraryBean.getBooks();
         System.out.println("Book(s) entered so far: " + booksList.size());
         for (int i = 0; i < booksList.size(); ++i) {
         System.out.println((i+1)+". " + booksList.get(i));
         }
         LibrarySessionBeanRemote libraryBean1 = 
         (LibrarySessionBeanRemote)ctx.lookup("LibrarySessionBean/remote");
         List<String> booksList1 = libraryBean1.getBooks();
         System.out.println(
         "***Using second lookup to get library stateless object***");
         System.out.println(
         "Book(s) entered so far: " + booksList1.size());
         for (int i = 0; i < booksList1.size(); ++i) {
            System.out.println((i+1)+". " + booksList1.get(i));
         }
      } catch (Exception e) {
         System.out.println("mmmmm"+e.getMessage());
         e.printStackTrace();
      }finally {
         try {
            if(brConsoleReader !=null){
               brConsoleReader.close();
            }
         } catch (IOException ex) {
            System.out.println("llll"+ex.getMessage());
         }
      }
   }  
}

After deployment, when I run EJBTester.java, I'm getting the following server logs...

23:48:59,933 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
23:49:00,190 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
23:49:00,250 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
23:49:02,505 INFO  [org.xnio] XNIO Version 3.0.3.GA
23:49:02,506 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
23:49:02,517 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
23:49:02,524 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
23:49:02,607 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
23:49:02,609 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
23:49:02,631 INFO  [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
23:49:02,637 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
23:49:02,644 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
23:49:02,653 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
23:49:02,677 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
23:49:02,686 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
23:49:02,771 INFO  [org.jboss.as.security] (MSC service thread 1-4) JBAS013100: Current PicketBox version=4.0.7.Final
23:49:03,811 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA
23:49:03,955 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
23:49:04,101 INFO  [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service
23:49:04,106 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
23:49:04,430 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-8) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8282
23:49:04,557 INFO  [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on localhost/127.0.0.1:4447
23:49:06,295 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
23:49:06,358 INFO  [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on /127.0.0.1:9999
23:49:06,368 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory C:\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\standalone\deployments
23:49:06,383 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found EnterpriseProject.ear in deployment directory. To trigger deployment create a file called EnterpriseProject.ear.dodeploy
23:49:06,384 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found LibraryEJB.jar in deployment directory. To trigger deployment create a file called LibraryEJB.jar.dodeploy
23:49:06,813 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "EnterpriseProject.ear"
23:49:06,816 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "LibraryEJB.jar"
23:49:07,029 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "EJBWebCielnt.war"
23:49:07,029 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "FirstEJBProject.jar"
23:49:07,160 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-5) JNDI bindings for session bean named LibrarySessionBean in deployment unit deployment "LibraryEJB.jar" are as follows:

	java:global/LibraryEJB/LibrarySessionBean!com.bhavesh.ejb.LibrarySessionBeanRemote
	java:app/LibraryEJB/LibrarySessionBean!com.bhavesh.ejb.LibrarySessionBeanRemote
	java:module/LibrarySessionBean!com.bhavesh.ejb.LibrarySessionBeanRemote
	java:jboss/exported/LibraryEJB/LibrarySessionBean!com.bhavesh.ejb.LibrarySessionBeanRemote
	java:global/LibraryEJB/LibrarySessionBean
	java:app/LibraryEJB/LibrarySessionBean
	java:module/LibrarySessionBean
23:49:07,574 INFO  [org.jboss.as] (MSC service thread 1-4) JBAS015951: Admin console listening on http://127.0.0.1:9990
23:49:07,575 INFO  [org.jboss.as] (MSC service thread 1-4) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 7942ms - Started 263 of 346 services (82 services are passive or on-demand)
23:49:07,620 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "LibraryEJB.jar"
23:49:07,621 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "EnterpriseProject.ear"
23:49:47,364 INFO  [org.jboss.as.naming] (Remoting "bhavesh-pc" task-1) JBAS011806: Channel end notification received, closing channel Channel ID 1da95cb3 (inbound) of Remoting connection 7c75144c to /127.0.0.1:54545
23:50:54,112 INFO  [org.jboss.as.naming] (Remoting "bhavesh-pc" task-3) JBAS011806: Channel end notification received, closing channel Channel ID 4e6ac79b (inbound) of Remoting connection 1a8b4ef6 to null

Please also observe property files if any mistake I made here...
And I also hv disabled the security-realm of JBoss to remove extra disturbances....

[Michael Remijan]

Typically if you want to use an EJB you use it inside of the EE server. However, if you are writing an stand alone application what you need to do is run you application inside the EE application client container. This is not something which is used much. Typically (and much more easy) is to expose your EJB functionality as a RESTful or full Web Service and have your client call them. However if you want to use the EJB, your application need to run inside the EE application client container. I don't know how JBoss does it, but basically what you do is execute a command which comes with your EE server to "wrap" your application with the EE server's application client container. You'll need to research how JBoss does this.

[Rob Spoor]

That's not necessary Michael. If the EJB is running in an existing application, then you can access them from standalone programs (or even other applications) through their remote interfaces. You need to look them up explicitly though, no injection.

[kannan vimal]

Hi how you  resolve this issue. i am facing same issue.

[Tim Holloway]

The EJB container (Wildfly, for example) publishes a JNDI service. Your standalone client just needs to be told the network address and port that the JNDI server listens on. Then your client submits a JNDI lookup request using the bean's logical identifier as the search string and the JNDI server will return a remote interface which serves as a proxy for the EJB. You invoke that proxy's methods and the corresponding method logic on the EJB server is executed.

Of course, EJB3 doesn't automatically create remote support objects like EJB version 1 did, so you do have to have explicitly defined the bean for remote invocation.

[kannan vimal]

This  below  is   my  client    invocation

final Hashtable<Object,Object> jndiProperties = new Hashtable<Object,Object>();  
	   jndiProperties.put(InitialContext.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");  
	   jndiProperties.put(InitialContext.PROVIDER_URL, "remote://localhost:4447");  
	   jndiProperties.put("jboss.naming.client.ejb.context", true);  
	    jndiProperties.put("jboss.naming.client.connect.options.org.xnio.Options.SASL_POLICY_NOPLAINTEXT", "false"); 
	   final Context context = new InitialContext(jndiProperties);  
		System.out.println("Initial context created");
		ExampleBeanRemote exampleBean = (ExampleBeanRemote) context.lookup("ExampleBean/remote");
System.out.println("Message from Bean :" + exampleBean.getMessage());

Errorlog



19:44:10,169 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
19:44:10,636 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
19:44:10,686 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
19:44:13,824 INFO  [org.xnio] XNIO Version 3.0.3.GA
19:44:13,826 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
19:44:13,835 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
19:44:13,843 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
19:44:13,888 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
19:44:13,908 INFO  [org.jboss.as.security] (MSC service thread 1-2) JBAS013100: Current PicketBox version=4.0.7.Final
19:44:13,991 INFO  [org.jboss.as.connector] (MSC service thread 1-5) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
19:44:14,783 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
19:44:14,940 INFO  [org.jboss.as.naming] (MSC service thread 1-5) JBAS011802: Starting Naming Service
19:44:14,955 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-7) JBAS015400: Bound mail session [java:jboss/mail/Default]
19:44:14,998 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-8) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
19:44:16,684 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
19:44:16,933 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-6) JBoss Web Services - Stack CXF Server 4.0.2.GA
19:44:17,613 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on localhost/127.0.0.1:4447
19:44:17,613 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on localhost/127.0.0.1:8999
19:44:17,618 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) JBAS015012: Started FileSystemDeploymentService for directory C:\param\learning\softwares\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\standalone\deployments
19:44:17,631 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found EjbExample.jar in deployment directory. To trigger deployment create a file called EjbExample.jar.dodeploy
19:44:17,988 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "EjbExample.jar"
19:44:18,032 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry javax.ejb-3.1.jar in "/C:/param/learning/softwares/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/EjbExample.jar"  does not point to a valid jar for a Class-Path reference.
19:44:18,033 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry jboss-client.jar in "/C:/param/learning/softwares/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/EjbExample.jar"  does not point to a valid jar for a Class-Path reference.
19:44:18,266 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named ExampleBean in deployment unit deployment "EjbExample.jar" are as follows:

java:global/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:app/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:module/ExampleBean!com.ejbs.ExampleBeanRemote
java:jboss/exported/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:global/EjbExample/ExampleBean!com.ejbs.ExampleBeanLocal
java:app/EjbExample/ExampleBean!com.ejbs.ExampleBeanLocal
java:module/ExampleBean!com.ejbs.ExampleBeanLocal

19:44:18,558 INFO  [org.jboss.as] (MSC service thread 1-7) JBAS015951: Admin console listening on http://127.0.0.1:8990
19:44:18,559 INFO  [org.jboss.as] (MSC service thread 1-7) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 9236ms - Started 173 of 250 services (76 services are passive or on-demand)
19:44:18,629 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "EjbExample.jar"
19:44:38,333 INFO  [org.jboss.as.naming] (Remoting "par-pc" task-4) JBAS011806: Channel end notification received, closing channel Channel ID 603862b4 (inbound) of Remoting connection 75629b42 to /127.0.0.1:49445

Kindly help  me to resolve