qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fraser Adams <fraser.ad...@blueyonder.co.uk>
Subject Re: [jira] [Created] (PROTON-564) Messenger.work doesn't receive messages
Date Wed, 16 Apr 2014 14:12:09 GMT
I must admit that I thought that recv was always necessary for what you are doing, am I not
correct that the python version of recv has an option with no parameter (the one that use
use in your XXX block) where the documentation says something like if no Message instance
is passed to recv then is just pops the message of the internal queue and discards it.

Sent from my iPad

On 16 Apr 2014, at 14:45, "Justin Ross (JIRA)" <jira@apache.org> wrote:

> Justin Ross created PROTON-564:
> ----------------------------------
> 
>             Summary: Messenger.work doesn't receive messages
>                 Key: PROTON-564
>                 URL: https://issues.apache.org/jira/browse/PROTON-564
>             Project: Qpid Proton
>          Issue Type: Bug
>    Affects Versions: 0.6, 0.7
>         Environment: Fedora 19, Python 2.7.5
>            Reporter: Justin Ross
> 
> 
> Sink:
> 
> {noformat}
> from proton import Messenger, Message
> 
> msgr = Messenger()
> msgr.start()
> 
> try:
>    msgr.subscribe("amqp://~0.0.0.0:50000")
> 
>    msg = Message()
> 
>    while True:
>        print "Tick; incoming={}".format(msgr.incoming)
> 
>        msgr.work()
>        # msgr.recv() XXX
> 
>        for i in range(msgr.incoming):
>            msgr.get(msg)
>            print(msg)
> finally:
>    msgr.stop()
> {noformat}
> 
> Source:
> 
> {noformat}
> from proton import Messenger, Message
> 
> msgr = Messenger()
> msgr.start()
> 
> try:
>    msg = Message()
>    msg.address = "amqp://0.0.0.0:50000/test"
> 
>    for i in range(10):
>        print "Tick {}".format(i)
> 
>        msg.body = "Message {}".format(i)
> 
>        msgr.put(msg)
>        msgr.send()
> finally:
>    msgr.stop()
> {noformat}
> 
> On 0.6, it blocks on one of the work calls with incoming always 0.  On 0.7, it keeps
looping through work calls with incoming always 0.  The source sends nothing.
> 
> Note the XXX bit in the sink.  If you uncomment that.  The sink consumes the messages.
> 
> The python API documentation says the following:
> 
> {noformat}
> Sends or receives any outstanding messages queued for a Messenger. This will block for
the indicated timeout. This method may also do I/O work other than sending and receiving messages.
For example, closing connections after messenger.stop() has been called.
> {noformat}
> 
> Based on that, I expect that I should not need to call recv.
> 
> 
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v6.2#6252)

Mime
View raw message