Hi Thanks for raising this. I have logged a ticket to make this easier in the future https://issues.apache.org/jira/browse/CAMEL-8413
On Fri, Feb 27, 2015 at 5:41 PM, ttom <[email protected]> wrote: > Hi, > > Ok, so I managed to get down to the bottom of it, and I'll just post this > for future reference. > > I found out that the StompComponent works just fine when there is not > requirement for SSL. So I went on to see if SSL is supported by it by > changing the potocol in the url from 'tcp' to 'ssl'. I was happy to see that > in the logs it actually tries to connect with the SSLEngine but it still > fails. After a little bit of digging I found out that the StompComponent is > not passing the SSLContext set in Camel to the stompjms-client, therefore > the stompjms-client uses the default SSLContext which is not configured with > the right truststore. I added these two options to the activemq startup > script, and evrything worked fine afterwards: > > -Djavax.net.ssl.trustStore=as-install/domains/domain1/config/cacerts.jks > -Djavax.net.ssl.trustStorePassword=changeit > > Tom > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/STOMP-SSL-bridge-between-two-ActiveMQ-Brokers-using-Camel-tp5763254p5763259.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
