On 24/05/16 13:22, Gordon Sim wrote:
On 24/05/16 12:20, Gordon Sim wrote:
On 24/05/16 10:39, Toralf Lund wrote:
Hi,
I have a program that sends messages to a topic exchange using the C++
messaging API. The messages are generally directed to a single receiver
queue. I thought it worked just fine (as always), but now I notice that
it gets stuck a short while after start-up. Simply put, the
sender.send() in the below "publish" routine never returns - not the
first time it's used, but after sending 50 or so nearly identical
messages.
How large are the messages?
The content size can vary, but for the tests I've been doing now, its
just 15 or 16 bytes. One string property of a similar size and one
uint32 property come in addition.
Is it possible that any of the queues to
which messages are delivered are flow controlled?
if you run:
qpid-config queues
and:
qpid-send -q
I think that should allow us to see if there is any queue near its limit.
qpid-config queues says
Queue Name Attributes
========================================
pgs.bocs.status --replicate=all --lvq-key=qpid.subject --argument
qpid.ha-uuid=1935a318-a308-49ff-bf56-3c618599349a --argument
qpid.last_value_queue=True --argument qpid.browse-only=True
The version of qpid-send I have doesn't seem to have a "-q" option. I
did try
qpid-send -a pgs.bocs.status -m 1
and it would also just sit there forever.
That would prevent the
broker 'completing' (aka acknowledging) the message, which would mean
that the producer would eventually run out of capacity.
The broker also runs in a cluser configuration with two nodes, by the
way. Could this cause similar issues? (I should have mentioned this
earlier, but I don't really think about it most of the time...)
- Toralf
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
