Remote Java EE Client with JNDI Lookup for Remote Session Beans

[Mohit G Gupta]

Source:OCP JavaEE 6 EJB Developer Study Notes by Ivan A Krizsan

I was trying to get reference to EJB(StatefulSession1Bean) using JNDI lookup for Remote-Client for same example as mentioned in 5.2.2. Remote Java EE Client with Dependency Injection with the below changes:

RemoteEJBClientServlet

@WebServlet(name = "RemoteEJBClientServlet", urlPatterns = "/test.do")
public class RemoteEJBClientServlet extends HttpServlet
{
/* Constant(s): */
private static final long serialVersionUID = 1L;
/* Instance variable(s): */
//@EJB(lookup = "java:global/RemoteSessionBean/StatefulSession1Bean")
private StatefulSession1Remote mRemoteSessionBean;
/**
* @see HttpServlet#doGet(HttpServletRequest request, HttpServletResponse response)
*/
@PostConstruct
public void intialize(){
	
	try{
		InitialContext theInitialContext=new InitialContext(); 
		mRemoteSessionBean=(StatefulSession1Remote)theInitialContext.lookup("java:global/RemoteSessionBean/StatefulSession1Bean");
		
	}catch (NamingException name){
		name.printStackTrace();
	}
	
}
@Override
protected void doGet(HttpServletRequest inRequest,
HttpServletResponse inResponse) throws ServletException, IOException
{
PrintWriter theResponseWriter = inResponse.getWriter();
String theRequestNameParam = inRequest.getParameter("name");
if (theRequestNameParam == null)
{
theRequestNameParam = "Anonymous";

}
String theResponse = mRemoteSessionBean.greeting(theRequestNameParam);
theResponseWriter.println("Response from the EJB: " + theResponse);
/* Process a list to examine parameter passing semantics. */
List<String> theList = new ArrayList<String>();
theList.add("string 1");
theList.add("string 2");
theList.add("last string");
mRemoteSessionBean.processList(theList);
/* Output list after EJB invocation. */
String theListStrings = "";
for (String theString : theList)
{
theListStrings += theString + ", ";
}
System.out.println("\nList after having invoked EJB processList: [" +
theListStrings + "]");
}
}

I am seeing the following exception in server logs:

SEVERE: javax.naming.NamingException: Lookup failed for 'java:global/RemoteSessionBean/StatefulSession1Bean' in SerialContext  [Root exception is javax.naming.NameNotFoundException: StatefulSession1Bean not found]
	at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:442)
	at javax.naming.InitialContext.lookup(InitialContext.java:392)
	at javax.naming.InitialContext.lookup(InitialContext.java:392)
	at com.ivan.scbcd6.client.RemoteEJBClientServlet.intialize(RemoteEJBClientServlet.java:36)
	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 com.sun.enterprise.container.common.impl.util.InjectionManagerImpl$3.run(InjectionManagerImpl.java:644)
	at java.security.AccessController.doPrivileged(Native Method)
	at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.invokeLifecycleMethod(InjectionManagerImpl.java:638)
	at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.inject(InjectionManagerImpl.java:408)
	at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.injectInstance(InjectionManagerImpl.java:141)
	at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.injectInstance(InjectionManagerImpl.java:127)
	at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.createManagedObject(InjectionManagerImpl.java:306)
	at com.sun.enterprise.web.WebContainer.createServletInstance(WebContainer.java:709)
	at com.sun.enterprise.web.WebModule.createServletInstance(WebModule.java:1937)
	at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1252)
	at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:1059)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:187)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:188)
	at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:641)
	at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:97)
	at com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:85)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:185)
	at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:325)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:226)
	at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:165)
	at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:791)
	at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693)
	at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:954)
	at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170)
	at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135)
	at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102)
	at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88)
	at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
	at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53)
	at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)
	at com.sun.grizzly.ContextTask.run(ContextTask.java:69)
	at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:330)
	at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:309)
	at java.lang.Thread.run(Thread.java:662)
Caused by: javax.naming.NameNotFoundException: StatefulSession1Bean not found

Please advise on the possible solution for the issue.

[Frits Walraven]

Hi Mohit,

Did you check the console log when starting up your application? You will find the global JNDI names being logged.

There is one small mistake though in your setup: In the PostConstruct method you only have JNDI access to "java:comp/env" (check chapter 4.6.1 table 1)

Regards,
Frits

[Mohit G Gupta]

Did you check the console log when starting up your application? You will find the global JNDI names being logged.

These were the JNDI names seen at startup of application:

INFO: Portable JNDI names for EJB StatefulSession1Bean : [java:global/RemoteSessionBean/StatefulSession1Bean!com.ivan.scbcd6.StatefulSession1Remote, java:global/RemoteSessionBean/StatefulSession1Bean]
INFO: Glassfish-specific (Non-portable) JNDI names for EJB StatefulSession1Bean : [com.ivan.scbcd6.StatefulSession1Remote, com.ivan.scbcd6.StatefulSession1Remote#com.ivan.scbcd6.StatefulSession1Remote]

There is one small mistake though in your setup: In the PostConstruct method you only have JNDI access to "java:comp/env" (check chapter 4.6.1 table 1)

I couldn't find any table under section:chapter 4.6.1 table 1(OCP JavaEE 6 EJB Developer Study Notes by Ivan A Krizsan,Version: April 8, 2012)
Also,I see that java:global,java:app,java:module can be used under PostConstruct method as mentioned under example (5.1.3. Local Session Bean Client with JNDI Lookup)

[Frits Walraven]

I couldn't find any table under section:chapter 4.6.1 table 1(

Sorry, I meant the ejb-specs chapter 4.6.1 table 1, but I now see that the PostConstruct is inside a Servlet (and not an EJB) so never mind this table as it is not relevant anymore...

Hmmmm... you are getting a NameNotFoundException, although it looks like you are using the correct name (btw I don't see the definition of your EJB)
Is the EJB packaged in the war or is it packaged in a separate jar?
Have you tried doing the lookup from the doGet() ? It looks like the global name is not yet available in the server.

Regards,
Frits

[Mohit G Gupta]

Hi Frits,

The Programs works fine now.
I was removing the RemoteSessionBean project from Add and Remove(Run on a Server) window on starting the RemoteEJBClientServlet on GlassFish Server.
The problem is resolved now

[Frits Walraven]

aha, ok, that was the problem!

Regards,
Frits