On Nov 4, 10:32 am, Corey Kaylor <co...@kaylors.net> wrote: > Because of the fact that rhino-queues requires that you stop any application > in order to inspect what's going on. The visualizer that was originally > built didn't seem to make sense to maintain going forward. There is a sample > linqpad file in the queues source that shows how to visualize what's going > on. It isn't comprehensive, but it should get you in the right direction. If > there is a way to at some point remove the requirement to stop the > application to inspect, then a visualizer tool to be more important IMO.
Hrm... linqpad is telling me my queue has a couple hundred messages in the Discarded subqueue, yet the file is over 80 megabytes. Now I read somewhere that esent does not shrink the database file automatically, so I tried esentutl /d but it did nothing. I am using the latest Rhino ESB with Esent 1.6. Should I even be concerned about this? On a related note, how do you manage the Error subqueue without taking the queue offline? For these reasons I am thinking of switching to MSMQ, but it does not support ICustomizeMessageHeaders which I need :( -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to rhino-tools-...@googlegroups.com. To unsubscribe from this group, send email to rhino-tools-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
