<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>If by "read" you mean "delivered to a client", then no, because exchanges don't do that sort of thing. Messages to consumers come from queues.<span><br><br>But that sounds like something the client should be concerned with because, regardless of the state of messages in a queue in the broker, the client knows whether it's receiving messages or not.<br><br>The admin client can happily report on any messages currently delivered to a queue. :)<br><span name="x"></span><br>Thanks!<br><br>Jon Brisbin<br>http//jbrisbin.com<br><span name="x"></span><br></span><br><hr id="zwchr"><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Meredith Gregory" <lgreg.meredith@gmail.com><br><b>To: </b>"Jon Brisbin" <jon@jbrisbin.com><br><b>Cc: </b>rabbitmq-discuss@lists.rabbitmq.com<br><b>Sent: </b>Thursday, May 26, 2011 3:09:26 PM<br><b>Subject: </b>Re: [rabbitmq-discuss] Journaling for RabbitMQ?<br><br>Dear Jon,<div><br></div><div>Thanks! Would that also log when a message was read?</div><div><br></div><div>Best wishes,</div><div><br></div><div>--greg<br><br><div class="gmail_quote">On Thu, May 26, 2011 at 12:26 PM, Jon Brisbin <span dir="ltr"><<a href="mailto:jon@jbrisbin.com" target="_blank">jon@jbrisbin.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div style="font-family: Times New Roman; font-size: 12pt; color: rgb(0, 0, 0);">I suspect it would take about 30 minutes to create a special journaled exchange type that simply logged every message that came through to a log file.<span> You'd need to use a custom exchange rather than a built-in version. That being said, it would act just like a built-in exchange type. But you probably wouldn't want to run something like this in production anyway, right?<br>
<br><span></span><br>Thanks!<br><br>Jon Brisbin<br>http//<a href="http://jbrisbin.com" target="_blank">jbrisbin.com</a><br><span></span><br></span><br><hr><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;">
<b>From: </b>"Meredith Gregory" <<a href="mailto:lgreg.meredith@gmail.com" target="_blank">lgreg.meredith@gmail.com</a>><br><b>To: </b><a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<b>Sent: </b>Thursday, May 26, 2011 1:55:20 PM<br><b>Subject: </b>[rabbitmq-discuss] Journaling for RabbitMQ?<div><div></div><div class="h5"><br><br>Dear Rabbitters,<div><br></div><div>i was working with a client recently and they asked whether RabbitMQ had a journaling feature. The client was used to working with MSMQ which has such a feature and allows them to get a view of queue usage history, such as message deposited to queue, message read from queue, etc. The question came up in the context of debugging a message processing code path where we couldn't readily tell whether the message had been deposited to the queue and was being nabbed by a dispatcher faster than we could see or whether the message was never arriving at the queue at all. The client observed that with a journaling feature there would be no need to introduce more debugging statements into application code. So, i'm passing their question along to you.</div>
<div><br></div><div>In this connection i will raise a point i've made before to this community. With such a journaling log i can take off-the-shelf tools and probe message traces for correctness properties. Specifically, i have already demonstrated with a little project called XTrace that with an xml-based message history format we can use schema conformance to probe message trace for properties. The basic idea is to encode a property as a schema. The beauty of this approach is that it is post facto and does not require a specific schema to govern message trace history. Rather, an application programmer devises schema to investigate the message trace history to look for conformance to protocol or validate a guess about where/how things might be going awry.</div>
<div><br></div><div>i mention this latter point in connection with the client's question to amplify the argument for the feature. Their sense of the separation of concerns and independent value for RabbitMQ is right on track and only the tip of the iceberg of what can be done.</div>
<div><br></div><div>Best wishes,</div><div><br></div><div>--greg<br clear="all"><br>-- <br>L.G. Meredith<br>Managing Partner<br>Biosimilarity LLC<br>7329 39th Ave SW<div>Seattle, WA 98136<br><br><a href="tel:%2B1%20206.650.3740" target="_blank">+1 206.650.3740</a><br>
<br><a href="http://biosimilarity.blogspot.com" target="_blank">http://biosimilarity.blogspot.com</a></div>
<br>
</div>
<br></div></div><div class="im">_______________________________________________<br>rabbitmq-discuss mailing list<br><a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br></div></blockquote><br></div></div></blockquote></div>
<br><br clear="all"><br>-- <br>L.G. Meredith<br>Managing Partner<br>Biosimilarity LLC<br>7329 39th Ave SW<div>Seattle, WA 98136<br><br>+1 206.650.3740<br><br><a href="http://biosimilarity.blogspot.com" target="_blank">http://biosimilarity.blogspot.com</a></div>
<br>
</div>
</blockquote><br></div></body></html>