configure the HTTPS transport
Configuration of the https transport is a bit different from that of the other transports since the implementation is based off the Tomcat connectors. One difference is that, in order to use SSL connections, the SSLImplementation attribute must be set and must always have the value org.jboss.remoting.transport.coyote.ssl.RemotingSSLImplementation. The SSLImplementation is used by the Tomcat connector to create ServerSocketFactorys, and RemotingSSLImplementation presents Tomcat with the ServerSocketFactory configured according to the options described above. An example of setting up https via service.xml configuration would be: jboss.remoting:service=ServerSocketFactory,type=SSL org.jboss.remoting.transport.coyote.ssl.RemotingSSLImplementation ${jboss.bind.address} 6669 org.jboss.test.remoting.transport.mock.MockServerInvocationHandler jboss.remoting:service=ServerSocketFactory,type=SSL See section SSLServerSocketFactoryService below for a discussion of the "jboss.remoting:service=ServerSocketFactory,type=SSL" MBean that appears in this configuration element. Note that the configuration for SSL support only works when using the java based http processor and not with the APR based transport. See section HTTP Invoker for more information on using the APR based transport.