Hi Hamid, If I were in your position, I would not try to debug two pieces of complex code at the same time.
I would recommend first trying to get the Windows ssl/tls calls working in a simple C program, completely separated from Qpid code. When that is working with your server and client certificates, you can concentrate on the integration with Qpid code. If you are pressed for time, I note that Steve Huston offered to help you on a consulting basis in a previous thread you started. He has done excellent work for the Qpid community and just happens to be the author of the code you are wading through. Cliff On Wed, Feb 1, 2012 at 10:03 AM, Hamid.Shahid <hamid2...@hotmail.com> wrote: > P.S. I have also tried it with the host name and get the following error; > > 2012-01-25 18:08:09 notice SSL negotiation failed to <host.name.com>:10170: > The target principal name is incorrect. > > Best Regards, > - Hamid > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/warning-Connect-failed-tp7229984p7243260.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:users-subscr...@qpid.apache.org > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscr...@qpid.apache.org
