4 Replies Latest reply on Mar 2, 2012 5:49 AM by ~= ziggy =~

    Jboss AS 6 - How to find an EJB via JNDI

    ~= ziggy =~ Newbie

      I am trying out a simple EJB 2.1 HelloWorld using Jboss AS 6. I created an EJB jar file with the following structure:












      I also created a client standalone java class to test the above ejb. I deployed the jar file using the Jboss 6 admin console under Applications > EJB2 jars and clicked on "Add new resource". When i add the jar file it gives me this message so i assume it was deployed correctly.


          Resource HelloWorldEjb.jar created successfully!


      Now when i run the client i get this error:


          log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

          javax.naming.NameNotFoundException: HelloHome not bound

              at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)

              at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)

              at org.jnp.server.NamingServer.getObject(NamingServer.java:785)

              at org.jnp.server.NamingServer.lookup(NamingServer.java:443)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

              at java.lang.reflect.Method.invoke(Method.java:597)

              at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)

              at sun.rmi.transport.Transport$1.run(Transport.java:159)

              at java.security.AccessController.doPrivileged(Native Method)

              at sun.rmi.transport.Transport.serviceCall(Transport.java:155)

              at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)

              at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)

              at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)

              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)

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

              at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)

              at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)

              at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)

              at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)

              at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:728)

              at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:688)

              at javax.naming.InitialContext.lookup(InitialContext.java:392)

              at client.HelloClient.main(HelloClient.java:58)

          Exception in thread "main" java.lang.NullPointerException

              at client.HelloClient.main(HelloClient.java:72)


      Initially i thought that i had to configure the JNDI resource for which the client will use to connect to find the EJB on the application server. Is this not necessary? The example i am using is using the EJB name in the lookup statement. Here is the section of the client code for making the connection. :


             Properties env = new Properties();


          env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory" );

          env.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");

          env.put(Context.PROVIDER_URL, "jnp://");


              //env = new InitialContext(env);


          InitialContext ctx = null;


          try {

              ctx = new InitialContext(env);

          } catch (NamingException e) {

              // TODO Auto-generated catch block




          Object obj = null;


          try {

              obj = ctx.lookup("HelloHome");

          } catch (NamingException e) {

              // TODO Auto-generated catch block




          HelloHome home = (HelloHome) javax.rmi.PortableRemoteObject.narrow(obj, HelloHome.class);


      And here is the  ejb-jar.xml file


      <?xml version="1.0" encoding="UTF-8"?>
























      One thing i found interesting is that when i compiled the client class, it refused to compile unless it had a reference to the HelloHome class. To resolve this i had to add the ejb jar file to the classpath of the client class. Is this how it is supposed to work? i.e. the ejb jar file needs to be on the classpath of the client?


      In terms of the jndi name used for the lookup, do i need to create a new name? In the above example, it looks the EJB name is used as a lookup.

        • 1. Re: Jboss AS 6 - How to find an EJB via JNDI
          ~= ziggy =~ Newbie



          I am currently going throught a book about EJB 3.0. Part of the introduction to EBJ 3.0 is to introduce me to the 2.0 variant hence why i am trying out this example. I think it does make sense to at least get a small understanding of how they work even if i am not planning on using EJB2.


          I had a look at the console for the list of deployed applications and i cant see my application on the EJB2.0 menu item. This i think means that the jar file has not deployed correctly. The Jboss logs do show that it was deployed (see 4th line below).


          16:36:50,982 INFO  [org.rhq.core.pc.PluginContainer] Plugin Container initialized.

          16:36:50,987 INFO  [org.jboss.on.embedded.manager.pc.PluginContainerResourceManager] Discovering Resources...

          16:36:50,988 INFO  [org.rhq.core.pc.inventory.AutoDiscoveryExecutor] Executing server discovery scan...

          16:36:53,920 INFO  [org.rhq.core.pc.inventory.InventoryManager] Detected new Server [Resource[id=-3, type=JBossAS Server, key=C:\bin\appservers\jboss-6.1.0.Final\server\default, name=JBoss AS 6 (default), parent=<null>, version=6.1.0.Final]] - adding to local inventory...

          16:36:54,032 INFO  [org.rhq.core.pc.inventory.AutoDiscoveryExecutor] Found 0 servers.

          16:36:54,032 INFO  [org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor] Running runtime discovery scan rooted at [platform]

          16:36:54,093 INFO  [org.rhq.core.pc.inventory.InventoryManager] Detected new Server [Resource[id=-4, type=JBoss AS JVM, key=JVM, name=JVM, parent=<null>, version=1.6.0_07]] - adding to local inventory...

          16:36:54,097 INFO  [org.rhq.plugins.jmx.JMXServerComponent] Starting connection to JMX Server JVM

          16:36:54,695 INFO  [org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor] Scanned [0] servers and found [0] total descendant Resources.


          Is there anything that looks wrong in the structure i described above?  

          • 2. Re: Jboss AS 6 - How to find an EJB via JNDI
            Roslan Amir Newbie

            Add this to your ejb-jar.xml:













            Add the descriptor file jboss.xml with the following entry to your META-INF directory:


            <jboss xmlns="http://www.jboss.com/xml/ns/javaee"











            Then in your client, the lookup should be:


            obj = ctx.lookup("ejb/HelloWorldEJB");



            Hope this works.






            • 4. Re: Jboss AS 6 - How to find an EJB via JNDI
              ~= ziggy =~ Newbie

              Is this possible with Jboss 7.0.2 or 7.1.0?