wrote:
> I'm confused about JMSPriority. My use case is simple:
>
> I have a bunch of fast servers that need to process slow (1 - 5
> second) jobs. I also have many slow servers for batch processing. All
> of these servers take jobs from the same queue.
>
> The slow servers
Using selectors is usually a better way of shaping traffic than JMSPriority.
On 2/25/07, Stefan Arentz <[EMAIL PROTECTED]> wrote:
I'm confused about JMSPriority. My use case is simple:
I have a bunch of fast servers that need to process slow (1 - 5
second) jobs. I also have many s
I'm confused about JMSPriority. My use case is simple:
I have a bunch of fast servers that need to process slow (1 - 5
second) jobs. I also have many slow servers for batch processing. All
of these servers take jobs from the same queue.
The slow servers use a selector like "type ==
