On 09/08/2011 03:37 PM, Bruno Matos wrote:
On Thu, 2011-09-08 at 14:51 +0100, Gordon Sim wrote:
On 09/07/2011 03:02 PM, Bruno Matos wrote:
Hello,
I have had some problems with a Windows client that doesn't consume
messages after some time of inactivity.
I made a simple test client to see if the problem exists in Linux
either. To be sure that they behave differently, I put the same simple
client waiting for a message in Windows and Linux, after 48h I sent a
message for the addressed bound by both clients and the Linux client
received the message but the Windows client didn't, the connection was
visible in broker and the queue had a message.
Either, after stopping the client, the connection was still visible in
broker.
I'm using version 0.10 in both broker and clients.
Does someone knows why this happens? Setting a heartbeat interval would
solve the problem?
Setting a heartbeat would certainly be a worthwhile experiment.
I'm already doing that. I will post the result when finished (more 24h).
It would
also be interesting to run qpid-stat -u before and after sending that
test message to see if the broker believes it has delivered the message.
In your test case, were the linux and windows client sharing a queue?
No, each one had its own.
When you say the queue still had a message, was that based on qpid-stat
-q or similar?
Yes, qpid-stat -q.
Was the message browseable?
I didn't try to read it. I can run a new test if you think it could help.
When your current test (with heartbeat) completes, if you still see the
same issue, run drain '<queue-name>; {mode:browse}' against the queue.
You can also run qpid-stat -u before and after sending the test message.
Both of these tests in effect determine whether the message was sent to
the client or not.
If the message has been sent (i.e. the delivery count is incremented for
the test message and the test message is not visible to a browser), then
perhaps a dump of the thread stacks on the client would be useful...
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
