I've been tracking down some performance issues on one of our queues. The queue
is hosted on an embedded broker. There is one producer and one consumer. All
messages sent to the queue are non-persistent. The producer initially will have
a burst of ~30k messages and then slow down to 100 messages
Thanks for the help. Works as expected now.
colomb
On Sat, Mar 10, 2012 at 7:29 AM, Rob Davies [via ActiveMQ] <
ml-node+s2283324n4462038...@n4.nabble.com> wrote:
> Unfortunately - when you disable persistence in the broker, it also
> prevents any use of storage to disk. I sugge
We are using an embedded broker producing non persistent messages. The
producer is quite fast and the consumers are usually able to keep up.
Sometimes, a consumer may slow down, and we would like to try ensure that
the producer isn't told to slow down if the broker fills up with messages.
\http:
That did it. Thanks for the quick response!
rajdavies wrote:
>
> Try turning flow control off - see
> http://activemq.apache.org/producer-flow-control.html
>
> cheers,
>
> Rob
> On 30 Sep 2008, at 17:19, colomb wrote:
>
>>
>> We are running some te
We are running some tests to evaluate upgrading to ActiveMQ v 5.1 from 4.1.1.
We are running the broker on one machine, and a message producer and
consumer on another. No persistence. Under 4.1.1, we get around 10,000
msgs/sec, however under 5.1.0 we only read 5000 msgs/sec. The tests are
bein
I believe we have resolved our problems. Clock synchronization issues across
the network was causing the clients to believe that the messages were
expired.
colomb wrote:
>
> bump
>
> Further info: All this is running in Java and the client machines are
> windows xp
bump
Further info: All this is running in Java and the client machines are
windows xp machines. Any suggestions?
colomb wrote:
>
> We are using activemq 4.1.1 and seeing some very strange issues. Our
> setup is as such: multiple client machines request information over queues
We are using activemq 4.1.1 and seeing some very strange issues. Our setup
is as such: multiple client machines request information over queues from a
central server. Over time, some of the client machines stop receiving
response messages from the central server! Restarting the queues, server
p