1 Reply Latest reply on Oct 25, 2012 2:19 PM by Phillip Rhodes

    EJB3 over HTTPS, on JBoss 4.2.3, client is still trying to use port 3873

    Phillip Rhodes Newbie

      I have a JBoss AS 4.2.3 server configured to use the Unified Invoker, and with SSL configured, per the instructions at:

       

      https://community.jboss.org/wiki/EJBJMSAndJNDIOverHTTPWithUnifiedInvoker

      and

      https://community.jboss.org/wiki/SSLSetup

       

      I access JNDI from the client, using the URL:

      https://servername:8443/unified-invoker/SSLJNDIFactory/?return-exception=true

       

      But the client calls are still trying to open a connection to the server on port 3873.

       

      So, my questions are:

       

      1. Why is it trying to connect on port 3873? 

      2. Does this mean that my calls are not actually going over https?

      3. Assuming the answer to (2) is "yes" then how do I fix this to ensure that all traffic on the remote call is using https?

       

      I do have the remote bindings specified in my ejb-jar like:

       

           <remote-binding>
              <jndi-name>TimeTellerBean/https</jndi-name>
              <client-bind-url>
                https://${jboss.bind.address}:8443/unified-invoker/SSLEjb3ServerInvokerServlet/?return-exception=true
              </client-bind-url>
            </remote-binding>

       

      But that doesn't seem to make any difference.

       

      Thanks in advance...