One other thing, and I imagine this would be pretty subjective, but knowing that RSB is pretty pluggable, how hard do you think it would be to write a new driver for say Rabbit MQ or another MQ? I haven't looked into the internals for the queue drivers yet, but I might give it a go if its not too difficult.
On Apr 6, 8:45 am, Chris Carter <[email protected]> wrote: > I didn't figure RSB was the cause, rather something I did in the > process from switching from RQ to MSMQ, though there really wasn't a > lot of involved in that :) Therein lies my disappointment with MSMQ > though, the fact than an external application can irreparably destroy > your MSMQ installation through the public API is just shameful. > > I'll try to get in touch with MS, thanks Ayende! > > On Apr 6, 1:59 am, Ayende Rahien <[email protected]> wrote: > > > > > Chris, > > I am sorry, I never heard about that error. > > Moreover, anything that RSB does is done with the public MSMQ API, it > > shouldn't be *possible *for it to corrupt the MSMQ installation. > > What happens if you are restarting the MSMQ service? > > > I think that you need to contact MS support for this, or try it on another > > machine, it is likely that your MSMQ installation is corrupt. > > > On Tue, Apr 6, 2010 at 12:44 AM, Chris Carter > > <[email protected]>wrote: > > > > Hi everyone, > > > > I'm seeing a really strange error that I'm having a difficult time > > > tracking down. I think its related to Rhino ESB, though I'm not sure > > > if the ESB is actually causing it, so I figured I'd ask and see if > > > anyone else has come across this in any other usages of MSMQ. I'm > > > using RSB as a client in a web app (ASP.NET, the client runs in the > > > background). The client talks to a windows service via the MSMQ > > > binding for RSB. Restarting the service never appears to have an > > > effect on MSMQ, neither does restarting IIS by hand. However, > > > whenever I actually restart the computer itself, MSMQ always refuses > > > to start back up, claiming that a "queue is in an inconsistent state". > > > > This has only started occurring since I switched from Rhino Queues to > > > MSMQ, which is why I'm asking here. The only information I've found > > > via the almighty Google are references to a problem in MSMQ 2.0 (this > > > problem is occurring in MSMQ 4.0). I've verified that Dispose is > > > being called on on the bus at shutdown, in both the service and the > > > web site. > > > > I'm getting frustrated with MSMQ that its this fragile, even if I'm > > > doing something wrong with this, it shouldn't destroy the entire MSMQ > > > installation (the only way I've found to resolve the error is to > > > uninstall and re-install MSMQ proper). > > > > Does anyone have any idea why this could be occurring? Thanks! > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "Rhino Tools Dev" group. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]<rhino-tools-dev%2Bunsubscribe@ > > > googlegroups.com> > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/rhino-tools-dev?hl=en. -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
