[rabbitmq-discuss] browse messages on a queue
jdetreville at vmware.com
Wed Mar 30 01:38:39 BST 2011
I've taken the conversation with Jim Irrer off-line. Sorry.
On Mar 21, 2011, at 9:14 AM, Jim Irrer wrote:
I was in the process of writing a plugin to get the same functionality:
What is the time frame for yours?
I had already been working some ideas for functionality, including writing to
a device or a database, and would like to know more details of what
you are doing.
Jim Irrer irrer at umich.edu<mailto:irrer at umich.edu> (734) 647-4409
University of Michigan Hospital Radiation Oncology
519 W. William St. Ann Arbor, MI 48103
On Mon, Mar 21, 2011 at 1:46 AM, John DeTreville <jdetreville at vmware.com<mailto:jdetreville at vmware.com>> wrote:
RabbitMQ lets you write your own plug-ins for storing queues. We're producing a few accompanying samples now, including one that stores all messages in a MySQL database. Its performance might be much lower than the standard queue implementation, but it would allow you to watch messages go by.
This MySQL plug-in should be out soon, but certainly not this month.
On Mar 18, 2011, at 10:33 AM, Kearney, Joe wrote:
> I'm interested in finding or writing a tool to monitor messages on a rabbit queue, in particular to be able to view messages waiting on the queue. The use case is for occasional monitoring and debugging; I'm not suggesting using a browse/read-only function in normal processing.
> This was raised on this mail group last July (http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2010-July/008004.html). Two pertinent quotes from that thread:
>> The only way you can get at the messages is through the normal AMQP methods that consume the messages (basic.consume and basic.get). But these are not simple read-only operations of the type you might want for monitoring of the messages within a queue.
>> it's actually quite hard to come up with a sensible semantics for it that isn't too constraining on implementations
> Has there been any progress on a built-in way to do this? Any thoughts on when/whether this might be introduced?
> Alternatively, can you comment on a sensible way to fake it? The naive implementation that springs to mind is simply to get a few messages from the head of the queue in a transaction and roll it back. Clearly this is more heavyweight than it need be, but are there any reasons that this behaviour should really be avoided for manual monitoring, until such a time as real read-only browsing is supported?
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com<mailto:rabbitmq-discuss at lists.rabbitmq.com>
rabbitmq-discuss mailing list
rabbitmq-discuss at lists.rabbitmq.com<mailto:rabbitmq-discuss at lists.rabbitmq.com>
More information about the rabbitmq-discuss