[rabbitmq-discuss] RabbitMQ 2.0 broker crashes

Scott Dupoy scottdupoy at gmail.com
Tue Dec 21 09:33:30 GMT 2010

Hi Matthew,

Thank you for your reply.

Making the assumption that we can't switch to a unix/linux distribution, is
it possible to change the size at which the *.rdq file rolls?  If this is
possible then at least we can (further) reduce the risk of a failure.


On 20 December 2010 18:27, Matthew Sackman <matthew at rabbitmq.com> wrote:

> On Mon, Dec 20, 2010 at 06:15:14PM +0000, Scott Dupoy wrote:
> > I've narrowed down the scenario when the crash occurs.  As the queue
> builds
> > up the msg_store_transient\0.rdq file is populated.  If I start the
> consumer
> > at this point everything is fine.  If the broker starts storing data in a
> > second database file (msg_store_transient\1.rdq) and then I start my
> > consumer then the crash occurs.  Procmon suggests a sharing violation
> with
> > one handle attempting to delete the 0.rdq file.
> Right. I think I can guess what's going on here, and it's not pretty.
> For various reasons, Rabbit can have the same file open multiple times.
> It can then decide to delete that file. Under unices, that's not a
> problem. However, apparently in general, on Windows, you can't ask for a
> file to be deleted if it's held open.
> This is not going to be a simple thing to fix. In all honesty, the best
> solution right now is for you not to run Rabbit under Windows. If you
> have to use a Windows host, then run a Linux VM within it.
> I'm pretty astonished that this hasn't been reported before. I guess
> that's likely an indication of the number of people that run RabbitMQ
> under Windows.
> Matthew
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20101221/41037318/attachment-0001.htm>

More information about the rabbitmq-discuss mailing list