Oops really sorry about that i missed a change from the commit. If you try and pull now you should have more luck, I confess to being a bit Git green.
On May 9, 3:27 am, Ayende Rahien <[email protected]> wrote: > Um, I can't compile your changes > Impl\AbstractRhinoServiceBusFacility.cs(52,21): error CS3005: Warning as > Error: Identifier > 'Rhino.ServiceBus.Impl.AbstractRhinoServiceBusFacility.ConsumeInTransaction' > differing only in case is not CLS-compliant > Impl\RhinoServiceBusFacility.cs(75,17): error CS0103: The name > 'consumeInTxn' does not exist in the current context > > On Sat, May 8, 2010 at 3:42 PM, philip <[email protected]> wrote: > > Ok pushed a patch. You now configure a ready for work queue on the > > load balancer: > > > <facility id="rhino.esb.loadbalancer" > > > <loadBalancer readyForWorkEndPoint="msmq://localhost/ > > rfwqueue" threadCount="1" endpoint="msmq://localhost/balancer" /> > > </facility> > > > On May 5, 4:07 pm, Ayende Rahien <[email protected]> wrote: > > > That would be great, thanks! > > > > On Wed, May 5, 2010 at 4:14 PM, philip <[email protected]> > > wrote: > > > > Yes i guess two queues would make sense. An AwaitingWork queue could > > > > be configurable on the LoadBalancer and the Workers would point at > > > > that. Does seem quite a big change but i can have a go at a patch if > > > > you like. > > > > > On May 5, 12:59 pm, Ayende Rahien <[email protected]> wrote: > > > > > that might work but wouldn't it be easier to have explicit two queues > > > > > > On Wednesday, May 5, 2010, philip <[email protected]> > > wrote: > > > > > > Of course that solution won't work as you can't send from workers > > to a > > > > > > LoadBalancer sub queue. > > > > > > > Another solution would be to move messages to an awiatingWorkers > > > > > > subqueue and read from there when assigning messages to workers. > > > > > > > On May 5, 11:43 am, philip <[email protected]> wrote: > > > > > >> When the loadbalancer is flooded with a high number of messages it > > can > > > > > >> get into a position where it cannot deal with the messages as > > quickly > > > > > >> as the messages are arriving, leading to overall badness. This is > > > > > >> because the loadbalancer has to read through the entire queue of > > > > > >> messages to find the ReadyToWork messages from the workers, which > > when > > > > > >> the queue is big can take a while. > > > > > > >> One possible fix might be to get the workers to send their > > ReadyToWork > > > > > >> messages to a subqueue and get the loadbalancer to watch the > > subqueue. > > > > > >> This way the loadbalancer should be able to deal out a message > > nearly > > > > > >> as soon as the ReadyToWork message arrives. > > > > > > >> -- > > > > > >> 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%[email protected]> > > <rhino-tools-dev%[email protected]<rhino-tools-dev%[email protected]> > > > > > . > > > > > >> For more options, visit this group athttp:// > > > > 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]<rhino-tools-dev%[email protected]> > > <rhino-tools-dev%[email protected]<rhino-tools-dev%[email protected]> > > > > > . > > > > > > For more options, visit this group athttp:// > > > > 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]<rhino-tools-dev%[email protected]> > > <rhino-tools-dev%[email protected]<rhino-tools-dev%[email protected]> > > > > > . > > > > > For more options, visit this group athttp:// > > > > 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]<rhino-tools-dev%[email protected]> > > <rhino-tools-dev%[email protected]<rhino-tools-dev%[email protected]> > > > > > . > > > > 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]<rhino-tools-dev%[email protected]> > > . > > > For more options, visit this group athttp:// > > 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]<rhino-tools-dev%[email protected]> > > . > > 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 > athttp://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.
