1 Reply Latest reply on Mar 5, 2004 3:39 PM by Marcelo Klein

    JNDI Failure Over HTTPS

    bigd Newbie

      Hi there,

      I'm having trouble getting EJB JNDI lookups to work over HTTPS.

      I am using JBoss 3.2.2 running on Win XP platform.

      I already have JNDI/EJB working over straight HTTP (having configured the HTTP Invoker for my bean).

      I have the tomcat SSL connector and keystore configured and can connect to the app server via


      This all works fine.

      To use HTTPS, I changed the client JNDI intial context URL to the https protocol and the web server SSL port. This worked fine. However when I disable the tomcat HTTP connector, the JNDI lookup fails (InitialContext.lookup()) with the following exception:

      Caused by: javax.naming.CommunicationException: Operation failed [Root exception is java.net.ConnectException: Connection refused: connect]
      at org.jboss.naming.interceptors.ExceptionInterceptor.invoke(ExceptionInterceptor.java:50)
      at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:45)
      at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:55)
      at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:85)
      at $Proxy1.lookup(Unknown Source)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:528)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507)
      at javax.naming.InitialContext.lookup(InitialContext.java:347)
      at com.metabit.jmstestbed.client.OrderClient.bootstrap(OrderClient.java:33)
      ... 1 more

      I tried debugging the client side invocation layer code and noticed that a http URL is being returned to the org.jboss.invocation.http.interfaces.HttpInvokerProxy class of the form: