Re: How to build qpid C++ client API without python

Thanks guys for your quick answer. I found libqpidclient.so libqpidmessaging.so will link to python. I will try to unlink it when build it. -- View this message in context: http://qpid.2158936.n2.nabble.com/How-to-build-qpid-C-client-API-without-python-tp7596285p7596291.html Sent from the Apac

How to build qpid C++ client API without python

Hi All, I am trying to build qpid C++ client apid, when I configure it I found it will use python. And I am sure I won't use python in my program. Why python is need in client C++ API, and how can I disable it when build qpid C++ client api? Thanks a lot! -- View this message in context: ht

Re: Why I can not build ssl componet

Seems gcc4.6 build lib required "lib" before the lib name. -- View this message in context: http://qpid.2158936.n2.nabble.com/Why-I-can-not-build-ssl-componet-tp7591440p7591442.html Sent from the Apache Qpid users mailing list archive at Nabble.com. ---

Re: Why I can not build ssl componet

PS: I can build ssl component with gcc 4.1.2. -- View this message in context: http://qpid.2158936.n2.nabble.com/Why-I-can-not-build-ssl-componet-tp7591440p7591441.html Sent from the Apache Qpid users mailing list archive at Nabble.com. ---

Why I can not build ssl componet

I am building the qpid c++ version with gcc 4.6.3 version and I found there is no sslconnector.so generated. I go through the build log, I found ssl under qpid/sys/ssl was not built, is there something I need to set to enable ssl build? Thanks. -- View this message in context: http://qpid.21

Re: connection is detached after receiver is created.

try { Receiver rcver = session.createReceiver(addr); .. } catch (const qpid::messaging::NoMessageAvailable& ex) { // No message, ignore exception and keep working print("Ignore no message available exception, and keep working."); } >From our app log, the connect

Re: connection is detached after receiver is created.

Thanks Gordon, I turn off the sending thread, it is still the same. I catch the exception qpid::messaging::NoMessageAvailable and just ignore it. -- View this message in context: http://qpid.2158936.n2.nabble.com/connection-is-detached-after-receiver-is-created-tp7587655p7587666.html Sent fro

Re: connection is detached after receiver is created.

correct, I have two separated thread for sending and receiving. Can not the session support multiple thread? -- View this message in context: http://qpid.2158936.n2.nabble.com/connection-is-detached-after-receiver-is-created-tp7587655p7587664.html Sent from the Apache Qpid users mailing list ar

Re: connection is detached after receiver is created.

from the bottom line logs, it seems session detached after sync. In what scenario client will detach session after session sync? -- View this message in context: http://qpid.2158936.n2.nabble.com/connection-is-detached-after-receiver-is-created-tp7587655p7587662.html Sent from the Apache Qpid u

Re: connection is detached after receiver is created.

related my app code for reading broadcast as following: try { Receiver rcver = session.createReceiver(addr); while(!stopFlag) { Message msg = rcver .fetch(Duration::SECOND * 10); //ProcessBroadcast(msg); message processing session.acknowledge(); } } catch() .

connection is detached after receiver is created.

I am using qpid c++ client API to connect to broker with SSL connection. but after I create the receiver I got session detached and connection closed, can someone shed some light on this? Apid logs as following: [Security] trace SENT [[33888 192.168.0.1:10170]]: Frame[BEbe; channel=1; {SessionAtt

Re: Failed to parse ssl URL

Hi Gordon, Thanks for response. I export explicitly QPID_LOAD_MODUL=$RS_LIB/sslconnector.so and I double checked this path is valid. My client application is running linux box with Qpid C++ client API to connect to remote broker. I added a debug log to Connector::registerFactory() after a protocol

Re: Failed to parse ssl URL

Thanks Gordon. I double checked my export QPID_SSL_CERT_DB=$RS_DATA/my_cert, the self signed certificate is valid one. I add some trace log and find this connection string amqp:ssl:192.168.20.23:5672 can be parsed correctly for seldom time about less than 5%. And I found TCP connector register Fa

Re: Failed to parse ssl URL

it is indeed the ssl, and I have configured the transport to ssl. But from the source code (Url.cpp:253): void Url::parse(const char* url) {parse(url, Address::TCP); } Seems it only supports TCP protocol. And the sslconnector.so module is loaded by default in Qpid. -- View this message in

Failed to parse ssl URL

I have an urgent issue with ssl connection.I am using qpid c++ client API to connect to broker with SSL connection. 1. I have setup required environment variables: export QPID_SSL_CERT_DB=$RS_DATA/my_cert export QPID_LOAD_MODUL=$RS_LIB/sslconnector.so export QPID_SSL_CERT_NAME="TEST"