OK, then the other things that may be worth checking are: On the server side, 1) deploy/http-invoker.sar/invoker.war/WEB-INF/web.xml Do you have JNDIFactorySSL servlet and servlet-mapping defined ? 2) deploy/http-invoker.sar/META-INF/jboss-service.xml Do you have HTTPProxyFactory defined which is referenced by the JNDIFactorySSL ? (typically under the name "jboss:service=invoker,type=https,target=Naming") On the client side, 3) Do you have the following system properties set when you run SenderHTTPQueue ? -Djavax.net.ssl.trustStore=<path_to_your_trust_store_file> -Dorg.jboss.security.ignoreHttpsHost=true Some of these are explained in the JBoss administration guide under the section "Accessing JNDI over HTTPS", and in the jboss4guide example (Namine/ex1). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136949#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...