Hi Brian, I noticed the same behavior with the JMSConnectionFactoryProvider, i.e. I could not figure out how to configure it to work with ActiveMQ SSL.
I ended up writing my own ActiveMQConnectionFactoryProvider which instantiates the ActiveMQSslConnectionFactory class. It was much easier for my deployments to bundle the ActiveMQ jars inside my new NAR anyway. Regards, -- Mike On Thu, Oct 26, 2017 at 11:36 AM, Joe Witt <[email protected]> wrote: > Brian - there just might not be a lot of folks running into it. You > might be in a situation where you'll have to dig in a good bit. If > you've not filed a JIRA with the stacktrace (and the > environmental/setup info you're mentioning here) already that would be > a good starting point that may also get additional eyes on. > > On Thu, Oct 26, 2017 at 10:13 AM, Brian Ghigiarelli <[email protected]> > wrote: > > ( Sorry for the duplication, but I figured this would be better sent to > the > > "users" alias vs. the "dev" alias... ) > > > > I'm having a bit of trouble getting an ActiveMQ v5.14 JMS consumer up and > > running over SSL with the new-ish ConsumeJMS processor, and was > wondering if > > anyone has any pointers on where to start. > > > > ConsumeJMS using a JMSConnectionFactoryProvider configured with a > > StandardSSLContextService and the MQ ConnectionFactory Implementation of > > "org.apache.activemq.ActiveMQSslConnectionFactory" throws the typical > > SSLHandshakeException ("unable to find valid certification path to > requested > > target") whenever I try to start the consume processor. > > > > However, I'm using that the same StandardSSLContextService for > GetJMSTopic > > (as well as in other processors) and everything's working fine. I'd like > to > > switch to ConsumeJMS for its shared resources and expression language > > support for the Broker URI, though. > > > > Any ideas on where to start troubleshooting? Has anyone else solved this? > > > > Thanks in advance, > > Brian >
