Using ActiveMQ > Configuring Transports > ActiveMQ Connection URIs > SSL Transport Reference
The SSL transport allows clients to connect to a remote ActiveMQ broker using SSL over a TCP socket.
`ssl://hostname:port?transportOptions**
The configuration options from TCP are relevant.
ssl://localhost:61616?trace=false
From version 5.4 any SSLServerSocket option may be set on a TransportConnection via ?transport.XXX, for example:
ssl://localhost:61616?transport.enabledCipherSuites=SSL_RSA_WITH_RC4_128_SHA,SSL_DH_anon_WITH_3DES_EDE_CBC_SHA ssl://localhost:61616?transport.needClientAuth=true
JMS clients can simply use the ActiveMQSslConnectionFactory together with an ssl:// broker url as the following Spring configuration illustrates
Unless the broker‘s SSL transport is configured for transport.needClientAuth=true, the client won’t need a keystore but requires a truststore in order to validate the broker's certificate.
Similar to the broker transport configuration you can pass on SSL transport options using ?socket.XXX, such as
You can also turn on SSL debug informations this way by adding:
-Djavax.net.debug=ssl
this way you can see what goes wrong and why you get connections closed.
“Be careful with multicast discovery”
If your XML configuration file contains the following and you wish to use SSL
<networkConnector uri="multicast://default"/>
Then you will currently need to comment that out.
The reason is to prevent ActiveMQ atempting to connect to itself - if you do this with a self-signed
certificate, you will get a constant spam of certificate_unknown
stacktraces to the console, as the broker is not configured with the
truststore,