the brokerUrl is the only property that should use the ssl scheme. Destinations are protocol agnostic. consider that the ActiveMQInitialContextFactory is really just a fancy hashmap with some predefined keys, it does not represent the state on the broker because the broker will create destinations on demand. So it is really just a simple facade in cases where jndi is required. peek at the implementation to further understand: https://github.com/apache/activemq/blob/trunk/activemq-client/src/main/java/org/apache/activemq/jndi/ActiveMQInitialContextFactory.java#L57
On 5 November 2013 10:38, mrich <[email protected]> wrote: > Thanks for the reply, > > I have gone with instantiating the SSL factory variant in the code as you > suggested, however I have always used JNDI to lookup a Destination (dynamic > queues), which doesn't seem to play nice with the SSL protocol. (Get a > malformed URL exception, unknownn protocol ssl). > > What is the best way to establish the connection to a Destination using SSL > ? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Instantiating-ActiveMQSslConnectionFactory-via-JNDI-SSL-tp4673824p4673893.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
