I'm using JBoss 4.0.3RC2 on Suse Linux. When I run the application with UseJBossWebLoader=true in jboss-service.xml file, the app is able to use JNDI to look up the Stateless Session bean. When I use the JBoss 4.0.3RC2 default of UseJBossWebLoader=false, the app attempt to look up the Session bean fails with the following:
javax.naming.NamingException: Could not dereference object [Root exception is javax.naming.CommunicationException: No such device [Root exception is java.net.SocketException: No such device]]
at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:1052)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:685)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:701)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at example.ejb.client.ServiceLocator.getHome(ServiceLocator.java:191)
at example.web.test.ExampleServlet.doGet(ExampleServlet.java:30)
.
.
.
When I switch the value of the UseJBossWebLoader flag, do I need to do take some other kind of action to make sure the client has access to the Stateless Session bean? I can still access it via the JMX Console.
Paula
