In the Java client, the SSL issues are very easy to analyse using the SSL debugging mode which can be switched on using the system property "javax.net.debug=ssl". It would be great to have something similar in the C++ client (and in the scripting languages clients build on top of the C++ client). But to my understanding the C++ client is for the SSL negotiation using the NSS library for which I never found such a nice debugging option.
Regards Jakub On Wed, Oct 23, 2013 at 6:15 PM, Trevor Vaughan <[email protected]>wrote: > No errors on the client side and adding trace to the QPID log didn't show > anything except for dropped connections. > > That's when I started using openssl s_server to debug the SSL portion. > > We're using 0.14-22 currently. > > > On Wed, Oct 23, 2013 at 11:46 AM, Gordon Sim <[email protected]> wrote: > > > On 10/23/2013 04:02 PM, Trevor Vaughan wrote: > > > >> amqp:ssl:myhost.mydomain:5671 > >> options << transport => 'ssl' > >> > >> But, no dice :-/ > >> > >> Thanks for the help though! > >> > > > > Do you get any errors on the client side? What if you export > > QPID_LOG_ENABLE=trace+ before trying to run the ruby client, does that > show > > up anything unusual looking? (I'm wondering if the sslconnector.so module > > is loaded, however if not then attempting to use ssl in the url should > > result in an error not a hang). > > > > What version of the client are you using? (I ran a simple test from ruby > > on trunk without a problem, so its either a different version or > different > > config in some way I think). > > > > > > ------------------------------**------------------------------**--------- > > To unsubscribe, e-mail: [email protected].**org< > [email protected]> > > For additional commands, e-mail: [email protected] > > > > > > > -- > Trevor Vaughan > Vice President, Onyx Point, Inc > (410) 541-6699 > [email protected] > > -- This account not approved for unencrypted proprietary information -- >
