EJB JNDI Not Being Published

[Dennis Hopfer]

From the Glassfish admin console I see nothing under the JNDI dropdown even though my test app seems to have been deployed. My understanding is that EJB apps automatically get pushed out to JNDI as part of the container's services. Is that wrong? Shouldn't it be visible there? I do see the app in the Applications drop down menu.

Any help?

[Jaikiran Pai]

What does the test app contain? What kind of EJBs?

[Dennis Hopfer]

Simple stateless session bean:

package org.test;

import javax.ejb.Stateless;
import javax.ejb.TransactionManagement;
import javax.ejb.TransactionManagementType;

/**
 * Session Bean implementation class Bean
 */
@Stateless
@TransactionManagement(TransactionManagementType.BEAN)
public class Bean implements BeanRemote 
{
	private String default_reply = "Default";
    /**
     * Default constructor. 
     */
    public Bean() 
    {
        // TODO Auto-generated constructor stub
    }

    @Override
    public String echoInput(String input)
    {
    	if(input==null || input.equals("")) return this.default_reply;
    	
    	return "You entered: "+input;
    }
}

package org.test;
import javax.ejb.Remote;

@Remote
public interface BeanRemote 
{
	public String echoInput(String input);
}

package org.test.client;

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

import org.test.*;

public class Client 
{
	final static String JNDI_NAME = "java:module/Bean";
	final static String SUBJECT_NAME = "Calculus";
	
	public static void main(String[] args)
	{
		try
		{	
			Context namingContext = new InitialContext();											
			
			BeanRemote controller = (BeanRemote)namingContext.lookup(JNDI_NAME);							
			
			System.out.println("JNDI lookup succeeded!");
		}
		catch(Exception e)
		{
			e.printStackTrace();
		}		
	}
}

Sun-EJB-Jar.xml (ripped off the web) looks like:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 9.0 EJB 3.0//EN" "http://www.sun.com/software/appserver/dtds/sun-ejb-jar_3_0-0.dtd">
<sun-ejb-jar>

<enterprise-beans>
	<ejb>
		<ejb-name>Bean</ejb-name>
		<jndi-name>bean</jndi-name>
		<bean-pool>
			<steady-pool-size>10</steady-pool-size>
			<resize-quantity>10</resize-quantity>
			<max-pool-size>100</max-pool-size>
			<pool-idle-timeout-in-seconds>600</pool-idle-timeout-in-seconds>
		</bean-pool>
		<bean-cache>
			<max-cache-size>100</max-cache-size>
			<resize-quantity>10</resize-quantity>
			<removal-timeout-in-seconds>3600</removal-timeout-in-seconds>
			<victim-selection-policy>LRU</victim-selection-policy>
		</bean-cache>
	</ejb>
	<cmp-resource>
		<jndi-name>jdbc/__default</jndi-name>
		<create-tables-at-deploy>true</create-tables-at-deploy>
		<drop-tables-at-undeploy>true</drop-tables-at-undeploy>
	</cmp-resource>
</enterprise-beans>

</sun-ejb-jar>

[Dennis Hopfer]

Help guys!

I'm total newb and I can't even get EJB 3.1 to work!

Help a newb out, for the Holidays!

[Dennis Hopfer]

Using latest build of Eclipse, Glassfish3 and EJB 3.1:

1) What should the MANIFEST.MF contain?

2) Does JNDI build-up/tear-down depend on sun-ejb-jar.xml file or does the container manage this automatically?

3) Merry Christmas!

[Jaikiran Pai]

Dennis Hopper wrote:
3) Merry Christmas!

Merry Christmas!

Dennis Hopper wrote:

1) What should the MANIFEST.MF contain?

MANIFEST.MF can be empty.

Dennis Hopper wrote:
2) Does JNDI build-up/tear-down depend on sun-ejb-jar.xml file or does the container manage this automatically?

The sun-ejb-jar.xml contains app server specific deployment configurations. Like the jndi name to which you want your beans to be bound to. That file is not mandatory. If you are using EJB3.1, then the file you posted earlier doesn't look relevant. It contains EJB2.x related constructs. Try removing that file altogether.

[Dennis Hopfer]

Hey Jaikiran!

So, yeah I tried pulling the XML file altogether and it still isn't grabbing the bean via JNDI. I'm not sure if the bean is published but I'm not using the right string to look it up or if it's just not being published as a JNDI resource. Any fool proof way to know for sure?

Thanks,

DH

[Celinio Fernandes]

when you deploy the application, you should see, in verbose mode, in the server logs the information about the portable or Glassfish-specific JNDI names for the EJB.
You don't see them ?

[Dennis Hopfer]

Only thing I see in the logs (I set everything to FINEST log setting) when I try and run the EJB is:

[#|2010-12-26T00:01:45.170-0500|INFO|oracle-glassfish3.0.1|javax.enterprise.system.tools.admin.org.glassfish.server|_ThreadID=21;_ThreadName=Thread-1;|JMXStartupService: Started JMXConnector, JMXService URL = service:jmx:rmi://Desktop:8686/jndi/rmi://Desktop:8686/jmxrmi|#]

Not sure what to make of it really.