Hello, I had a similar issue in a custom OSGi environment. When evaluating the transport connection parameters, ActiveMQ uses an IntrospectionSupport package to look at the transport connection parameters and create a map of key value pairs. As part of this IntrospectionSupport package, it does a check to see if the class you are working with is SSLServerSocket. In this case we are not (the clazz is org.apache.activemq.transport.failover.FailoverTransport), but javax.net.ssl.SSLServerSocket needs to be on the classpath in order to evaulate.
In the environment I was in, javax.net.ssl was not available to the bundle in the OSGi container. Adding javax.net.ssl to the environment solved this issue. This may not be the reason for your failure, but just wanted to share my experience. Joe -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-8-FailoverTransport-Invalid-connect-parameters-tp4669644p4675343.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
