-
1. Re: Does SlowConsumers flag work correctly?
schmidp Jun 5, 2008 5:10 AM (in response to szhigunov)Is there any way to turn prefetch completely, so all messages which are not received would be visible to all consumers?
We have the same requirement, so I'm interested in an answer as well :-)
Best regards,
Philipp Schmid -
2. Re: Does SlowConsumers flag work correctly?
ataylor Jun 5, 2008 6:00 AM (in response to szhigunov)Setting slow consumers=true has the effect of setting the prefetch size to 1. This means that the server will only deliver 1 message the client side buffer. Once the client has consumed this message and the buffer is empty the client notifies the server and it starts redelivering.
-
3. Re: Does SlowConsumers flag work correctly?
szhigunov Jun 5, 2008 1:05 PM (in response to szhigunov)In my scenario I always consume one big message per session (in its own XA transaction). So the behavior described above (PrefetchSize=1) seems like unnecessary overhead: I want to consume one message; I download two to the client, use one; release the other.
Is there the way to tell the system I need just one at a time?
If not, is that a big overhead?
Does JBM eagerly downloads the entire message (say 10 Megabytes) or just handler, so the rest of the body gets downloaded on demand (when the application actually starts reading)? -
4. Re: Does SlowConsumers flag work correctly?
timfox Jun 8, 2008 4:05 AM (in response to szhigunov)"szhigunov" wrote:
Is there the way to tell the system I need just one at a time?
Not for JBM 1.x.
In JBM 2.0 it allows the behaviour you expect, but that won't be ready for production for some time.