activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryce Prescott (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-3989) ActiveMQSslConnectionFactory.setKeyAndTrustManagers does not work with failover enabled using 5.7 snapshot Jars
Date Thu, 23 Aug 2012 16:50:41 GMT

     [ https://issues.apache.org/jira/browse/AMQ-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bryce Prescott updated AMQ-3989:
--------------------------------

    Attachment: ActiveMQFailoverTest.zip

Here it is.

It contains a readme.txt file with very simple instructions on running it.

The SSL failover fails with a certificate_unknown error using
ActiveMQSslConnectionFactory.setKeyAndTrustManagers

If, however, that line of code is commented out and Thread.setSslContext is used instead it
does work.
                
> 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
>             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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message