Sorry, the previous post was truncated by the forum. Here it is again: 1. Create an embedded ActiveMQ TCP broker with failover enabled
2. Connect to the embedded ActiveMQ TCP broker with failover URL 3. Stop connection and embedded ActiveMQ TCP broker 4. Create an embedded ActiveMQ SSL broker with failover enabled 5. Connect to the embedded ActiveMQ SSL broker with failover URL (THIS IS WHERE THE CERTIFICATE UNKNOWN ERROR OCCURS) Optionally, a non-failover ActiveMQ SSL broker can be started and connected to in order to prove that SSL and the certificates work. No need to create producers or consumers since the error occurs before getting that far. -- View this message in context: http://activemq.2283324.n4.nabble.com/Certificate-unknown-error-AFTER-failover-enabled-tp4655212p4655315.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
