1 Reply Latest reply: Mar 15, 2012 3:44 PM by Ron Sigal RSS

    Accessing EJB over HTTP

    Mario Rossi Newbie

      I followed the instructions here

       

      http://community.jboss.org/wiki/EJB3OverHTTPHTTPSInJBossAS-5

       

      and here

       

      http://community.jboss.org/wiki/AccessingEJB3soverHTTPHTTPS

       

       

      The client (an applet) receives the response from the EJB but the Java console on the browser still print some connections to 3873 port (in bold)

       

       

      DEBUGEJB - BEFORE LOOKUP

      network: Connecting http://192.168.13.118:8080/invoker/JMXInvokerServlet with proxy=DIRECT

      network: Connecting http://192.168.13.118:8080/ with proxy=DIRECT

      basic: JNLP2ClassLoader.findClass: [Ljava.lang.Object;: try again ..

      basic: JNLP2ClassLoader.findClass: [Ljava.lang.Object;: try again ..

      network: Connecting http://192.168.13.118:3873/ with proxy=DIRECT

      DEBUGEJB - AFTER LOOKUP

      network: Connecting http://192.168.13.118:3873/ with proxy=DIRECT

      DEBUGEJB - BEFORE EJB INVOCATION

      network: Connecting http://192.168.13.118:3873/ with proxy=DIRECT

      basic: JNLP2ClassLoader.findClass: [...]

      DEBUGEJB - AFTER EJB INVOCATION

       

      Why does the applet still use the 3873 port ? What can I check ?

       

       

      The client set the following properties:

       

      props.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.HttpNamingContextFactory");

      props.put(Context.PROVIDER_URL, "http://192.168.13.118:8080/invoker/JNDIFactory");

      props.put(Context.URL_PKG_PREFIXES, "org.jboss.naming");

       

      Server side setting on EJB:

       

      @Stateless

      @RemoteBinding(clientBindUrl="http://192.168.13.118:8080/servlet-invoker/ServerInvokerServlet")

      @Remote(MyClass.class)

      @SecurityDomain("other")

       

      And i configured the server as described in the links before.