I've got the hint that this is related to
https://issues.apache.org/activemq/browse/AMQ-2567
I've now tried a current Snapshot of ActiveMQ 5.4 which contains the fix for
it and it works as expected!
Many thanks to Rudolf Janz for pointing me in that direction and to Gary
Tully for helping me
Which raises my next question:
When can we expect a release of ActiveMQ 5.3.1 or 5.4?
Christoph Kutzinski wrote:
I've got the hint that this is related to
https://issues.apache.org/activemq/browse/AMQ-2567
I've now tried a current Snapshot of ActiveMQ 5.4 which contains the fix
for it
Watch the list of outstanding issues for 5.3.1
https://issues.apache.org/activemq/secure/IssueNavigator.jspa?reset=truemode=hidesorter/order=DESCsorter/field=priorityresolution=-1pid=10520fixfor=12183
When these are resolved we can do a release.
On 1 February 2010 13:57, Christoph Kutzinski
Hi,
let me first describe my use-case as it is probably a little bit different from
the usual JMS use case:
We have a single process which fills a JMS queue from a pool of available items
(say we have 50 items total).
The we have n consumers (lets say 2) which read the items from the queue in
No,
sorry no simple testcase and currently don't have the time to create one.
As I can the see from the 'Prefetch 0' in the web console, prefetchSize
seems to get noticed from ActiveMQ. However, it doesn't seem to have any
effect on the dispatched queue.
I can only provide this code snippet
An additional observation:
The size of the dispacthed queue seems also to be equal the (largest) number
of messages I received in a row. E.g. if I received 5 message the webconsole
looks like this:
Enqueues 10; Dequeues 5; Dispatched 10; Dispatched Queue 5
If I receive 10 messages later from
