Rhino Service Bus: Store and Forward?

[ColinA]

Is it possible to useRhino Service Bus with Rhino Queues in a 'store and forward' configuration?

For example, lets say I have two nodes, A and B. If B is down, I don't want any of the messages that A is trying to send to B to be lost - so A should cache outbound messages in a durable, local queue before attempting to send them to the remote queue.

Is this possible with Rhino Service Bus with Rhino Queues?

Regards,

Colin

[Corey Kaylor]

Yes, store and forward is the only thing that is supported with rhino queues.

--
You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group.
To view this discussion on the web visit https://groups.google.com/d/msg/rhino-tools-dev/-/3ZwREewwepoJ.
To post to this group, send email to rhino-t...@googlegroups.com.
To unsubscribe from this group, send email to rhino-tools-d...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.

[Nathan]

Where are the messages stored? Ive read (albeit, in a post from 2008)
that Rhino Queues is not durable, and messages are only kept in
memory. Has that changed? Will queued messages survive an app
restart?

Thanks,

Nathan

On Oct 24, 2:13 pm, Corey Kaylor <co...@kaylors.net> wrote:
> Yes, store and forward is the only thing that is supported with rhino
> queues.
>

[Kaylor Mail]

Rhino queues has always been durable.

[Jason Meckley]

RQ uses Rhino.PHT (persisent hash table) for storage. PHT is built on top of esent.

[Corey Kaylor]

RQ uses esent directly. The PHT is for subscription storage.

On Thu, Nov 17, 2011 at 6:26 AM, Jason Meckley <jasonm...@gmail.com> wrote:

RQ uses Rhino.PHT (persisent hash table) for storage. PHT is built on top of esent.

--
You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group.

To view this discussion on the web visit https://groups.google.com/d/msg/rhino-tools-dev/-/HrkWj7Emn9oJ.

[Jason Meckley]

good to know, thanks Corey

[Nathan]

Thanks for the clarification. Ive since built a test app to learn
more of RQ and it looks really nice. One problem I am having in the
store-forward pattern is how to purge the message once its been
forwarded. Inspecting via Linqpad I do see that the messages are
getting "consumed" but the size of the the queue directory never
shrinks. Is there a command to reclaim that space?

Ive tried

sender.NumberOfMessagesToKeepInProcessedQueues = 0;
sender.NumberOfMessagesToKeepOutgoingQueues = 0;
sender.NumberOfReceivedMessagesToKeep = 0;

but they dont have any effect on the directory size.

[Ozan Yurtseven]

Hi Nathan,

My config below, after this settings RQ purging old data. If you wait
you can see on console output purging old data string.

qm.NumberOfReceivedMessagesToKeep = 100;
qm.NumberOfMessagesToKeepOutgoingQueues = 150;
qm.OldestMessageInProcessedQueues = TimeSpan.FromMinutes(1);
qm.OldestMessageInOutgoingQueues = TimeSpan.FromMinutes(1);

But i have a questions for you.

1- How did you reach this properties
sender.NumberOfMessagesToKeepInProcessedQueues and others
I check all methods bur queuemanager is private and i had to change rq
code and i wrote qm accessor. Can you send your implementation.

2- Another thing i can't do LinqPad query. Can you explain how to run
linq pad query.

Thanks.

2011/11/18 Nathan <nsk...@gmail.com>:

> --
> You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group.