1 Reply Latest reply on Sep 9, 2006 10:06 PM by Andrew Rubinger

    NameNotFoundException Service not bound

    Ravi K Newbie

      I'm using the http invoker and all my ejb2.1 lookup goes over https. now ejb3 beans deploy fine (according to the JMX console) but the lookup fails with the usual message. For e.g. when i look up AddEntity

      Here's part of the the JMX view with 2.1 and 3.0 beans


      Properties props = new Properties();
      props.put("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
      props.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces");
      props.put("java.naming.provider.url", "localhost");
      InitialContext ctx = new InitialContext(props);
      // THIS WORKS, returns Home interface
      Object object = ctx.lookup("AddEntity");
      // THIS FAILS, with a not found/bound exception
      CalculatorService remote = (CalculatorService)ctx.lookup("CalculatorService/remote");

      It seems like there's something in the configuration jungle that I must have turned off that causes this OR the lookup name I'm using different than 'CalculatorService'. Is there a separate EJBInvokerServlet for 3.0 beans? Any insight is appreciated.

      Of course this works fine in example mode when deployed with the 'all' server instance.