[
https://issues.apache.org/jira/browse/PROTON-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim closed PROTON-425.
-----------------------------
Resolution: Not A Problem
This is an issue with qpidd, not proton. As the messages are not explicitly
accepted, even though settled, they are never being dequeued.
See https://issues.apache.org/jira/browse/QPID-5170
> [Messenger] messenger can only browse qpidd's queues
> ----------------------------------------------------
>
> Key: PROTON-425
> URL: https://issues.apache.org/jira/browse/PROTON-425
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: 0.5
> Reporter: Ken Giusti
> Fix For: 0.6
>
>
> I have a simple queue on the qpidd broker, which holds one message:
> $ qpid-stat -q
> Queues
> queue dur autoDel excl msg msgIn msgOut
> bytes bytesIn bytesOut cons bind
> ============================================================================
> KENQ 1 1
> 0 65 65 0 0 1
> Attempting to consume from that queue using the messenger recv example:
> $ ./examples/messenger/py/recv.py amqp://127.0.0.1:5672/KENQ
> None (no subject) {u'spout-id': u'7fe1a726-b1bc-40e6-b91f-51cf34136f33:0'}
> None
> recv.py gets the message, but it is never removed from qpidd's queue:
> $ qpid-stat -q
> Queues
> queue dur autoDel excl msg msgIn msgOut
> bytes bytesIn bytesOut cons bind
> ============================================================================
> KENQ 1 1
> 0 65 65 0 0 1
> Seems like messenger can only browse qpidd's queues.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
