uld be prefetch limit - the default is 1000 - would be worth trying
> with 1
>
> On 15 Dec 2009, at 13:54, Diego Castorina wrote:
>
>>
>> I went a little bit further with my tests:
>> -the queue was containing 5219 messages and no one of them was
>> distrib
I went a little bit further with my tests:
-the queue was containing 5219 messages and no one of them was distributed
to any of the listeners (I set the maxConcurrentConsumers property in the
DefaultMessageContainerListener of Spring to 20)
-I added 50 messages to the queue
-the first 50 message o
Yes, it is.
rajdavies wrote:
>
> Is this version 5.3 ?
> On 15 Dec 2009, at 10:50, Diego Castorina wrote:
>
>>
>> We are experiencing similar problems.
>> We are informed by the mbean queueSize property that around 5000
>> messages
>> are still in
We are experiencing similar problems.
We are informed by the mbean queueSize property that around 5000 messages
are still in the queue.
This is the configuration of our broker:
The reason why it does not work is that you forgot to add the attribute
start="true" to the broker declaration.
When the AMQConnectionFactory tries to connect to the broker it does not
find it (since you have not started it yet) and than creates and start a new
one using default values. The new br
