Non-Durable Queues & Non-Persistent messages using MassTransit and RabbitMQ

[wtfe...@g.cofc.edu]

Hello,

Is there any way to configure Mass Transit to not store messages on the hard disk? We have a security constraint that we cannot store messages on the disk since they will contain personal information.  But at the same time we don't want to store the entire error_queue in memory since it would eventually use it all up if a service goes offline and never comes back up. So how about it. Is there any way to configure Mass Transit to not use durable queues and to not store messages in an error queue?

I was reading through the documentation but I could not find any information regarding the above.

Thanks!

[Chris Patterson]

You could modify the message type to not save the message, but if the system crashes you will lose everything. You would have to modify the MSMQ transports to send non-durable messages, that's not something that's built in by default (I don't think, I've never thought of doing non-durable messaging as the cost is not worth it if you aren't durable).

Consider using at-rest disk encryption (either whole disc, or encrypt the folder for MSMQ and run the service with access to encryption) or something else. Security of data at rest is pretty easy to deal with if you just use the right tools.

--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-dis...@googlegroups.com.
To post to this group, send email to masstrans...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/40ae5f23-3cc3-4d10-b9f4-6fc8c9c046ad%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[wtfe...@g.cofc.edu]

That is fine if we lose everything when the system crashes. Is there any way to make MT not store messages in an Error_Queue in RabbitMQ? Or can we just make the error_queue not durable?  I have found the sections of code in the source where MT declares queues using RabbitMQ but I cannot find where the error queue is being declared. I could just simply turn the durable value to false in the error_queue declaration if I can just find it.

Thanks 

On Thursday, October 17, 2013 10:08:20 PM UTC-4, Chris Patterson wrote:

You could modify the message type to not save the message, but if the system crashes you will lose everything. You would have to modify the MSMQ transports to send non-durable messages, that's not something that's built in by default (I don't think, I've never thought of doing non-durable messaging as the cost is not worth it if you aren't durable).

Consider using at-rest disk encryption (either whole disc, or encrypt the folder for MSMQ and run the service with access to encryption) or something else. Security of data at rest is pretty easy to deal with if you just use the right tools.

On Thu, Oct 17, 2013 at 6:06 PM, <wtfe...@g.cofc.edu> wrote:

Hello,

Is there any way to configure Mass Transit to not store messages on the hard disk? We have a security constraint that we cannot store messages on the disk since they will contain personal information.  But at the same time we don't want to store the entire error_queue in memory since it would eventually use it all up if a service goes offline and never comes back up. So how about it. Is there any way to configure Mass Transit to not use durable queues and to not store messages in an error queue?

I was reading through the documentation but I could not find any information regarding the above.

Thanks!

--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-discuss+unsub...@googlegroups.com.