Re: CorrelationId

2014-12-10 Thread xavier
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 -

Re: CorrelationId

2014-12-10 Thread Dominic Evans
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

2014-12-10 Thread xavier
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;

Observations on the performance of the proton event model

2014-12-10 Thread Ken Giusti
Hi, I've been working on a simple patch to qpidd that ports the AMQP 1.0 module to the new event interface provided by proton 0.8. See https://issues.apache.org/jira/browse/QPID-6255 for the patch. With the above patch, I've noticed a pretty consistent small drop in overall qpidd performance

RE: CorrelationId

2014-12-10 Thread xavier
Dominic, I posted my code for the community. But I progress, and all works, but I saw, with this code, the memory grow up in each time, I did this function: pn_link_t* link; pn_messenger_subscribe(msgConsumer, amqp://127.0.0.1:5672/queue://myqueue); link = pn_messenger_get_link(msgConsumer,

[jira] [Resolved] (PROTON-750) Have distinct API to indicate SSL layer is not really implemented

2014-12-10 Thread Andrew Stitcher (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-750. Resolution: Fixed Fix Version/s: 0.9 Have distinct API to indicate SSL layer is not

[jira] [Created] (PROTON-769) Simplify the trace flag logic by only keeping a single copy

2014-12-10 Thread Andrew Stitcher (JIRA)
Andrew Stitcher created PROTON-769: -- Summary: Simplify the trace flag logic by only keeping a single copy Key: PROTON-769 URL: https://issues.apache.org/jira/browse/PROTON-769 Project: Qpid Proton

[jira] [Created] (PROTON-770) Refactor Proton C to eliminate the pn_dispatcher_t class

2014-12-10 Thread Andrew Stitcher (JIRA)
Andrew Stitcher created PROTON-770: -- Summary: Refactor Proton C to eliminate the pn_dispatcher_t class Key: PROTON-770 URL: https://issues.apache.org/jira/browse/PROTON-770 Project: Qpid Proton

Re: Observations on the performance of the proton event model

2014-12-10 Thread Andrew Stitcher
An off the cuff thought - worth what you paid for it - On Wed, 2014-12-10 at 11:23 -0500, Ken Giusti wrote: ... Furthermore, I think the event API would benefit from a way to 'opt-in' to specific events. For example, for qpidd we would not want to receive PN_TRANSPORT nor

[jira] [Created] (PROTON-771) AMQP and SASL performatives are not validated against correct frame type

2014-12-10 Thread Andrew Stitcher (JIRA)
Andrew Stitcher created PROTON-771: -- Summary: AMQP and SASL performatives are not validated against correct frame type Key: PROTON-771 URL: https://issues.apache.org/jira/browse/PROTON-771 Project:

Re: Observations on the performance of the proton event model

2014-12-10 Thread Rafael Schloming
On Wed, Dec 10, 2014 at 11:23 AM, Ken Giusti kgiu...@redhat.com wrote: Hi, I've been working on a simple patch to qpidd that ports the AMQP 1.0 module to the new event interface provided by proton 0.8. See https://issues.apache.org/jira/browse/QPID-6255 for the patch. With the above

Re: Observations on the performance of the proton event model

2014-12-10 Thread Rafael Schloming
On Wed, Dec 10, 2014 at 5:10 PM, Andrew Stitcher astitc...@redhat.com wrote: An off the cuff thought - worth what you paid for it - On Wed, 2014-12-10 at 11:23 -0500, Ken Giusti wrote: ... Furthermore, I think the event API would benefit from a way to 'opt-in' to specific events. For

[jira] [Commented] (PROTON-769) Simplify the trace flag logic by only keeping a single copy

2014-12-10 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14242113#comment-14242113 ] ASF subversion and git services commented on PROTON-769: Commit

[jira] [Commented] (PROTON-771) AMQP and SASL performatives are not validated against correct frame type

2014-12-10 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14242115#comment-14242115 ] ASF subversion and git services commented on PROTON-771: Commit

[jira] [Commented] (PROTON-770) Refactor Proton C to eliminate the pn_dispatcher_t class

2014-12-10 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14242114#comment-14242114 ] ASF subversion and git services commented on PROTON-770: Commit

[jira] [Commented] (PROTON-696) The header file usage needs some improvement

2014-12-10 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14242112#comment-14242112 ] ASF subversion and git services commented on PROTON-696: Commit

[jira] [Created] (PROTON-772) Remove all direct printing to stdout and stderr.

2014-12-10 Thread Alan Conway (JIRA)
Alan Conway created PROTON-772: -- Summary: Remove all direct printing to stdout and stderr. Key: PROTON-772 URL: https://issues.apache.org/jira/browse/PROTON-772 Project: Qpid Proton Issue Type: