[
https://issues.apache.org/jira/browse/AMQ-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-3989:
-------------------------------
Assignee: Gary Tully
> ActiveMQSslConnectionFactory.setKeyAndTrustManagers does not work with
> failover enabled using 5.7 snapshot Jars
> ---------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-3989
> URL: https://issues.apache.org/jira/browse/AMQ-3989
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.5.1, 5.6.0, 5.7.0
> Environment: GNU/Linux (shouldn't matter too much) using a SslBroker
> embedded in Java code running in Tomcat (I've tested it without Tomcat and
> the same thing happens).
> Reporter: Bryce Prescott
> Assignee: Gary Tully
> Fix For: 5.7.0
>
> Attachments: ActiveMQFailoverTest.zip
>
>
> I've been using ActiveMQ with SSL enabled for months now. After enabling
> failover on the broker and connecting using a failover URL I get this error:
> certificate_unknown
> I find two workaround: one using System.setProperty, the other using
> Thread.setSslContext. But these are workarounds and I'd rather do things the
> appropriate way.
> This is similar to the issue posted in this JIRA:
> https://issues.apache.org/jira/browse/AMQ-3785. The issue is marked as
> resolved but I am still getting that error using 5.7 snapshot Jars.
> I'll attach a zip file containing very simple code and test case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
