JNDI Name binding in JBOSS 5.1.0 Beta.

[Hardik Mehta]

Hi,

I am following the MasteringEJB4thEdition book, which I downloaded from The Server Site website.

There is a simple example of HelloBean, which works perfectly with GlassFish V3 app server. The same example when deployed on JBOSS fails because of JNDI name lookup.

Is there any rule how the JNDI lookup names in JBOSS are decided if we don't provide any ? I found while googling that it is "<ear-file-name>/<Bean-class-name>/remote" but it doesn't work for me.

Here is the bean

package com.hardik.stateless;
import javax.ejb.Stateless;
import javax.ejb.Remote




@Stateless
@Remote(Hello.class)
public class HelloBean implements Hello {

	public String hello() {
		System.out.println("hello()");
        return "Hello, World!";
	}

}

Here is the client I am using:

package com.hardik.stateless;

import javax.naming.Context;
import javax.naming.InitialContext;


/**
 * This is an example of client code which invokes 
 * methods on a simple, remote stateless session bean
 * @author hardik
 *
 */
public class HelloClient {
	
	public static void main(String[] args) throws Exception {
		
		Context ctx = new InitialContext();
		// works for Glassfish
		//Hello hello = (Hello) ctx.lookup("com.hardik.stateless.Hello");
		// doesn't  work for JBOSS
		Hello hello = (Hello) ctx.lookup("hello-bean/HelloBean/remote");
		
		System.out.println(hello.hello());
	}

}

Here is the error I get while executing the client

$ wsrunclient.sh -Djava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory -Djava.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces -Djava.naming.provider.url=jnp://localhost:1099  -cp "lib/hello-bean.jar:dist/hello-client.jar:/home/hardik/apps/jboss/client/*"  com.hardik.stateless.HelloClient
log4j:WARN No appenders could be found for logger (org.jnp.interfaces.TimedSocketFactory).
log4j:WARN Please initialize the log4j system properly.
Exception in thread "main" javax.naming.NameNotFoundException: hello-bean 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:396)
        at sun.reflect.GeneratedMethodAccessor260.invoke(Unknown Source)
        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:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        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:722)
        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:682)
        at javax.naming.InitialContext.lookup(InitialContext.java:392)
        at com.hardik.stateless.HelloClient.main(Unknown Source)

[Jaikiran Pai]

Do you deploy it in a EAR? If not, it's just the BeanClassName/remote. In any case, the server console will show the exact JNDI name that's being used for the bean, when the bean is being deployed. Something like:

12:45:08,367 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:

        SecureManagementView/remote - EJB3.x Default Remote Business Interface
        SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView - EJB3.x Remote Business Interface

What do you see on your console?

[Hardik Mehta]

Hi thanks for the quick reply.

I checked the deployment logs, and I found something like this...

2009-06-22 11:06:31,195 DEBUG [org.jboss.ejb3.common.registrar.plugin.mc.Ejb3McRegistrar] (main) Returning from name "org.jboss.ejb3.JndiReg
istrar.Session.SLSBJndiRegistrar": org.jboss.ejb3.proxy.jndiregistrar.JndiStatelessSessionRegistrar@3a669a
2009-06-22 11:06:31,195 DEBUG [org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase] (main) Found Session Bean: HelloBean
2009-06-22 11:06:31,197 INFO  [org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase] (main) Binding the following Entries in Global J
NDI:


2009-06-22 11:06:31,215 DEBUG [org.jboss.ejb.txtimer.EJBTimerServiceImpl] (main) createTimerService: org.jboss.ejb.txtimer.TimerServiceImpl@
591d98
2009-06-22 11:06:31,237 WARN  [org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerEJB] (main) Ingore ejb deployment with null classn
ame: org.jboss.metadata.ejb.jboss.JBossSessionBeanMetaData@bebe0782{HelloBean}
2009-06-22 11:06:31,239 DEBUG [org.jboss.deployers.structure.spi.helpers.AbstractDeploymentContext] (main) Added component jboss.jacc:id="vf
szip:/home/hardik/apps/jboss-5.1.0.Beta1/server/default/deploy/hello-bean.ear/",service=jacc to vfszip:/home/hardik/apps/jboss-5.1.0.Beta1/s
erver/default/deploy/hello-bean.ear/

Look the part after Global JNDI: is empty.

[Jaikiran Pai]

Do you have any ejb-jar.xml or jboss.xml in the jar? If yes, please post its contents. Also see this thread for a similar issue

[Hardik Mehta]

Thanks Jaikiran,

Exactly this was the problem, I was missing namespace information in the ejb-jar.xml.


Now I changed it according to your link..

<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar version="3.0" 
	xmlns="http://java.sun.com/xml/ns/javaee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
    http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd">
</ejb-jar>

Now it works as expected.