0 Replies Latest reply on Apr 14, 2005 5:36 PM by David Chisholm

    Need help with javax.naming.CommunicationException

    David Chisholm Newbie

      I had several EJBs deployed in a single module, and JNDI lookup worked fine. After splitting some of the EJBs into a separate jar and adding a new module to my EAR for the new EJB jar, the JNDI lookup fails for the EJBs in the new module.

      All EJBs are local stateless session beans, and so network calls should not be involved, yet the root cause of the Comm. exception is:

      java.net.SocketTimeoutException: Receive timed out
      at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:971)
      at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1052)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:450)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:443)
      at javax.naming.InitialContext.lookup(InitialContext.java:347)

      I'm using XDoclet to generate the ejb-jar.xml and jboss.xml, and I'm using JBoss 3.0.4.

      Is there any additional J2EE or JBoss configuration parameters that I need to configure to get JNDI lookups to work for the new module?

      Thanks for any help