Hi,
Thanks Andreas and Gordon.
Following this note
"Note: The deprecated qpid::client API will be removed in the next release.
Users should instead use the Qpid Messaging API."

I've decided to use qpid::messaging API instead of qpid::client api.

I've followed the edvice of Andreas,

std:string broker("IP:port");
Connection connection(broker, "{transport:ssl}"); 

But still having the same error (if I replace ssl with tcp the error doesn't
occur but I need to work with ssl)

I compile with this command:

g++ -I/....../abelaid/QpidBuild/RH5_PKG/Debug/include/
-L/....../abelaid/QpidBuild/RH5_PKG/Debug/lib -lqpidmessaging
-L/....../abelaid/QpidBuild/RH5_PKG/Debug/lib/qpid/client -lsslconnector -o
conn3 Connection3.cpp

And when I run my binary (with the log activated):


2014-08-26 12:19:04 [System] debug Exception constructed: Failed: NSS error
[-8174] (qpid/sys/ssl/util.cpp:103)
2014-08-26 12:19:04 [Security] error Failed to initialise SSL connector:
Failed: NSS error [-8174] (qpid/sys/ssl/util.cpp:103)
2014-08-26 12:19:04 [System] debug Exception constructed: Failed: NSS error
[-8174] (qpid/sys/ssl/util.cpp:103)
2014-08-26 12:19:04 [Security] error Failed to initialise SSL connector:
Failed: NSS error [-8174] (qpid/sys/ssl/util.cpp:103)
2014-08-26 12:19:04 [Client] debug Created connection 90.162.253.101:10170
with {transport:ssl}
2014-08-26 12:19:04 [Client] debug Starting connection,
urls=[90.162.253.101:10170]
2014-08-26 12:19:04 [Client] info Trying to connect to
90.162.253.101:10170...
2014-08-26 12:19:04 [Client] debug Created IO thread: 0
2014-08-26 12:19:04 [System] debug Exception constructed: Unknown protocol:
ssl (qpid/client/Connector.cpp:52)
Unknown protocol: ssl (qpid/client/Connector.cpp:52)

Thanks again.




--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Unknown-protocol-ssl-for-C-client-tp7611980p7612547.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to