Re: C++ client question

Hi Gordon, this is exactly what I wanted to get. I tried to do it through a pointer to a Session and it just did not work: class MySender { private: Connection *pConn; Session *pSess; public: MySender() {pConn = NULL; pSess = NULL;} ~MySender() { if (pConn != NULL) delete pConn;}

Re: C++ Plugin modules

On Thu, 2013-06-27 at 14:11 +0100, Gordon Sim wrote: > On 06/27/2013 06:46 AM, Andrew Stitcher wrote: > > I think that we should minimise our use of modules and try to remove > > those we already have - either stop building them as plugins or > > remove them altogether. > > > > Thoughts? > > Perso

Re: C++ client API.. How to set uint8 value in FieldTable?

On 06/27/2013 04:12 PM, trivedi_ravi13 wrote: Is it possible to set uint8 value in FieldTable class? setInt() method seem to be taking uint32_t You can set the value to a shared_pointer to an instance of Unsigned8Value, e.g. ft.set("my-key", boost::shared_ptr(new Unsigned8Value(i))); Howeve

Re: Receiver fetch vs get

Hi Pavel, You are right, I just updated the client libraries to 0.22 and the problem disappeared. Thank you, Regards. On 27-06-2013 16:25, Pavel Moravec wrote: Hi Bruno, I think you hit https://issues.apache.org/jira/browse/QPID-4595 that is fixed in qpid 0.21. Kind regards, Pavel -

Re: Receiver fetch vs get

Hi Bruno, I think you hit https://issues.apache.org/jira/browse/QPID-4595 that is fixed in qpid 0.21. Kind regards, Pavel - Original Message - > From: "Bruno Matos" > To: users@qpid.apache.org > Sent: Thursday, June 27, 2013 5:19:38 PM > Subject: Receiver fetch vs get > > Hi, > > I'm

Receiver fetch vs get

Hi, I'm using the C++ Qpid Broker v. 0.22 and client libraries 0.20. In the client I have a Receiver configured to listen events like bindings and unbindings with a defined capacity of 100. If I use the fetch method, after reading 100 messages or a little more, the following messages never rea

C++ client API.. How to set uint8 value in FieldTable?

Is it possible to set uint8 value in FieldTable class? setInt() method seem to be taking uint32_t -- View this message in context: http://qpid.2158936.n2.nabble.com/C-client-API-How-to-set-uint8-value-in-FieldTable-tp7594657.html Sent from the Apache Qpid users mailing list archive at Nabble.co

Re: C++ client question

On 06/27/2013 02:37 PM, Petr Parýzek wrote: Hi, I was try to encapsulate qpid client into this simple class class MySender { private: Connection *pConn; public: MySender() {pConn = NULL;} ~MySender() { if (pConn != NULL) delete pConn;} void Send(const char *Addr, const char *M

Re: C++ client question

Hi Petr, just a guess: aren't you destroying instance of your class meantime? I.e. having declared in a block and trying to use its Session outside the block or so? Can you access the instance of your class and its connection at the place when calling Send() method for the second time? Btw. y

C++ client question

Hi, I was try to encapsulate qpid client into this simple class class MySender { private: Connection *pConn; public: MySender() {pConn = NULL;} ~MySender() { if (pConn != NULL) delete pConn;} void Send(const char *Addr, const char *Msg) {if (pConn == NULL) pConn = new Connect

Re: C++ Plugin modules

On 06/27/2013 06:46 AM, Andrew Stitcher wrote: I think that we should minimise our use of modules and try to remove those we already have - either stop building them as plugins or remove them altogether. Thoughts? Personally I'm not overly concerned whether a module is compiled in to qpidd its

Re: Dynamic Route and Duplicate Detection

The qpid broker already does loop-suppression to prevent messages from taking the same path more than once. The reason you get two messages is because you have created a topology with redundant paths in it (i.e. there are two distinct paths from each sender to each receiver). Your receiver wi