RE: CorrelationId

= pn_message(); pn_messenger_get(msgConsumer, message); . . pn_message_free(message); } pn_link_close(link); From: Dominic Evans [via Qpid] [mailto:ml-node+s2158936n7617738...@n2.nabble.com] Sent: jeudi 18 décembre 2014 17:44 To: Millieret, Xavier Subject: RE: CorrelationId xavier wrote Perhaps I must

RE: CorrelationId

xavier wrote > Perhaps I must free some object, but in debug mode and checking the > memory, memory grow up, each time I do pn_messenger_subscribe, > pn_messenger_recv, etc. did you try running your binary via valgrind memcheck? -- View this message in context: http://qpid.2158936.n2.nabble.c

RE: CorrelationId

Hi, Any body have an idea about this? The new version of the lib will fix this, or it's my code? regards -- View this message in context: http://qpid.2158936.n2.nabble.com/CorrelationId-tp7614606p7617531.html Sent from the Apache Qpid Proton mailing list archive at Nabble.com.

RE: CorrelationId

7...@n2.nabble.com] Sent: mercredi 10 décembre 2014 12:07 To: Millieret, Xavier Subject: Re: CorrelationId Hi Xavier, so 006FE360 is your messenger that is responsible for subscribing and receiving the messages based upon the selector. xavier wrote [006FE360]: -> SASL [006FE360]:0 -> @sas

RE: CorrelationId

Here the right code //Doing this one time pn_messenger_t* msgConsumer= pn_messenger(NULL); pn_messenger_set_timeout (msgConsumer, 1000); pn_messenger_set_blocking (msgConsumer, true); pn_messenger_set_incoming_window (msgConsumer, 1); // Doing this more time pn_link_t* link; pn_messenger_subscribe

RE: CorrelationId

m: Dominic Evans [via Qpid] [mailto:ml-node+s2158936n7617327...@n2.nabble.com] Sent: mercredi 10 décembre 2014 12:07 To: Millieret, Xavier Subject: Re: CorrelationId Hi Xavier, so 006FE360 is your messenger that is responsible for subscribing and receiving the messages based upon the selector. xa

Re: CorrelationId

Hi Xavier, so 006FE360 is your messenger that is responsible for subscribing and receiving the messages based upon the selector. xavier wrote > [006FE360]: -> SASL > [006FE360]:0 -> @sasl-init(65) [mechanism=:PLAIN, > initial-response=b"\x00emc2\x00emc2"] > [006FE360]: <- SASL > [006FE360]:0 <-

Re: CorrelationId

Hi Dominic, I set PN_TRACE_FRM=1 and here my trace. [006FC110]: -> SASL [006FC110]:0 -> @sasl-init(65) [mechanism=:PLAIN, initial-response=b"\x00emc2\x00emc2"] [006FC110]: <- SASL [006FC110]:0 <- @sasl-mechanisms(64) [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS, :PLAIN]] [006FC110]:0 <- @sas

Re: CorrelationId

Hi Dominic unfortunately, it 's does not work!! I try your idea, see my code (I move the pn_link_detach() and pn_link_open() in all my code, but .) Here my code: // Init one time to use many time pn_messenger_t* msgConsumer= pn_messenger(NULL); pn_messenger_set_timeout (msgConsumer, 1000); pn

Re: CorrelationId

Hi Xavier, xavier wrote > I posted my solution, it works, but I did some performance test, and it's > not very good, I found why. In my solution, I start, and stop for any > receiver the messenger, because if I don't do this, with my code (posted) > I receive one time, the message with a filter (

Re: CorrelationId

Hi all, I found the solution (for ActiveMq, with a connector in AMQP, and a connector with openwire), so I share the solution. I used the idea of Dominic Evans, so If I want to get a message from a filter (for example correlationId ), I did this: pn_messenger_t* msgConsumer= pn_messenger(NULL); p

Re: CorrelationId

Hi all, I re start to work on this issue!!! and it is not work! So here my last code: // get recv link pn_link_t* link = pn_messenger_get_link (messengerConsumer, myAdress, false); // get the source link, is't it, I saw, before doing that on the the activemq's log, than the filter is: the source

Re: CorrelationId

On Thu, Oct 9, 2014 at 8:44 AM, Dominic Evans wrote: > fadams wrote > > On 08/10/14 18:49, Rafael Schloming wrote: > >> Actually I think it is possible to do this with messenger now that > >> dominic's patches are in. You can access the link associated with any > >> given > >> address using pn_me

Re: CorrelationId

fadams wrote > On 08/10/14 18:49, Rafael Schloming wrote: >> Actually I think it is possible to do this with messenger now that >> dominic's patches are in. You can access the link associated with any >> given >> address using pn_messenger_get_link() and configure it however you want >> to. >> >> -

Re: CorrelationId

Hi all, pn_messenger_get_link is not in the 0.7 qpid lib, right? Is it in the next release 0.8 ? If yes do you have any date for it, and code sample, with? Thanks a lot regards -- View this message in context: http://qpid.2158936.n2.nabble.com/CorrelationId-tp7614606p7614826.html Sent from

Re: CorrelationId

Hi all, Thanks a lot for your answer, I am busy today, but I will try this, and send you me feedback. Regards -- View this message in context: http://qpid.2158936.n2.nabble.com/CorrelationId-tp7614606p7614825.html Sent from the Apache Qpid Proton mailing list archive at Nabble.com.

Re: CorrelationId

On 08/10/14 18:49, Rafael Schloming wrote: On Wed, Oct 8, 2014 at 1:30 PM, Fraser Adams wrote: On 08/10/14 08:16, xavier wrote: Hi Frase, Thanks for your explanation, but here, my code: In the requester: char * corrId; . . pn_bytes_t bytes = pn_bytes(correlationId.size(), corrId)

Re: CorrelationId

On Wed, Oct 8, 2014 at 1:30 PM, Fraser Adams wrote: > On 08/10/14 08:16, xavier wrote: > >> Hi Frase, >> >> Thanks for your explanation, but here, my code: >> >> In the requester: >> >> char * corrId; >> . >> . >> pn_bytes_t bytes = pn_bytes(correlationId.size(), corrId); >> pn_atom_t id

Re: CorrelationId

On 08/10/14 08:16, xavier wrote: Hi Frase, Thanks for your explanation, but here, my code: In the requester: char * corrId; . . pn_bytes_t bytes = pn_bytes(correlationId.size(), corrId); pn_atom_t id; id.type = PN_STRING; id.u.as_bytes = bytes; pn_message_set_correlation_id(message, i

Re: CorrelationId

Hi Frase, Thanks for your explanation, but here, my code: In the requester: char * corrId; . . pn_bytes_t bytes = pn_bytes(correlationId.size(), corrId); pn_atom_t id; id.type = PN_STRING; id.u.as_bytes = bytes; pn_message_set_correlation_id(message, id); and after, send it pn_messenge

Re: CorrelationId

On 07/10/14 08:04, xavier wrote: Hi all, Thanks you for your reply, help? So if I understand properly, to do that with messenger is not trivial??? But I don't understand why, because with the pattern request/reply in asynchronous mode, and with dedicated queue, we must have this feature. isn't i

Re: CorrelationId

Hi all, Thanks you for your reply, help? So if I understand properly, to do that with messenger is not trivial??? But I don't understand why, because with the pattern request/reply in asynchronous mode, and with dedicated queue, we must have this feature. isn't it? So to do that must I take some t

Re: CorrelationId

Certainly for the C based messenger there currently only seems to be support for basic link configuration, so unfortunately doing anything more sophisticated than addressing a named node seems to be out at the moment. I do keep mentioning it regularly, but nobody seems to be biting :-) So it'

Re: CorrelationId

ActiveMQ currently uses an AMQP filter to specify the selector string the broker should use for the consumer. I dont believe Messenger currently supports specifying filters, however I have next to no experience with Messenger so perhaps someone with more knowledge can comment. Robbie On 2 October