Without looking too deep. I'm pretty sure running the Starbucks sample integration tests several times can reproduce this issue. I noticed the behavior myself (not getting all published messages) when working to remove the Castle dependency and trying to ensure no regressions. I'm not personally using MSMQ or the load balancer so Ayende might need to help with this to confirm.
On a separate note, I also noticed that there should be support to specify an alternate configuration for the ready for work queue, but that configuration value is never used, so I'm doubtful it really works. -- 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-dev@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.
