I think this is a case of https://issues.apache.org/jira/browse/AMQ-3785
On 22 August 2012 16:12, bryce <br...@mbsys.us> wrote:
> The problem is now solved...
>
> It turns out that ActiveMQSslConnectionFactory.setKeyAndTrustManagers does
> not work (at least in this context).
>
> Replacing that the following does work:
>
> System.setProperty("javax.net.ssl.keyStore",KEY_STORE_FILE_NAME);
> System.setProperty("javax.net.ssl.keyStorePassword",KEY_STORE_PASSWORD);
> System.setProperty("javax.net.ssl.trustStore",TRUST_STORE_FILE_NAME);
> System.setProperty("javax.net.ssl.trustStorePassword",TRUST_STORE_PASSWORD);
>
> For Mirth (in case anyone out there is using it) I added command line flags
> (-Djavax...) corresponding to the ones above to the vmoptions file.
>
> Just wanted to let everyone know in case they have similar problems.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Certificate-unknown-error-AFTER-failover-enabled-tp4655212p4655433.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
http://fusesource.com
http://blog.garytully.com
