Ok, I just tried it on 4.0.5.GA. I have the following: - a stateless bean with following remote bindings annotations: @RemoteBindings({ @RemoteBinding(clientBindUrl="sslsocket://0.0.0.0:3843", jndiBinding="TestService/remotessl"), @RemoteBinding(jndiBinding="TestService/remote") }) - the ssl-service.xml and a keystore packaged within the ejb jar (exactly as shown in the SSL tuturial); the ejb-jar is packaged in an ear - a service client that uses TestService/remotessl jndi name; it works; the clien console tells me it uses port 3843. If using TestService/remote; the client console tells me that that port 3873 (default Remote EJB3 Invoker port) I then enable the Binding Service Manager in jboss-service.xml and point it to sample-bindings.xml file in the jboss/server/default/conf folder where the only thing I override is the port for the ssl invoker defined in the ssl-service.xml as follows: | <service-bindings> | | <server name="ports-default"> | | <service-config name="jboss.remoting:type=Connector,transport=socket3843,handler=ejb3" | delegateClass="org.jboss.services.binding.AttributeMappingDelegate"> | <delegate-config> | <attribute name="InvokerLocator">sslsocket://${jboss.bind.address}:3833</attribute> | </delegate-config> | <binding port="3833"/> | </service-config> | | </server> | | </service-bindings> | If I run the ssl client now, I get a org.jboss.remoting.CannotConnectException, but the console tells me the client still tries to connect to 3843, as opposed to the override port 3833. I suspect the service is now available over SSL at the new port, but client does not understand that it has to connect to that new port. Would deploying the ssl-service.xml in the default/conf folder work? Regards Sergiu View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983942#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...