I am using ActiveMQ version 5.0.0 . I create a stomp producer and add
messages to a queue (does not matter if the messages are added as persistent
or not, same behavior). I create a consumer to read from that queue. Once
the consumer begins to read, the producer is slowed down drastically ( from
First I would like to thank Rob for solving that specific issue, I have not
yet had time to grab the latest release but once I do I will most definitely
be using that feature.
James - I appreciate your quick response to my concerns. You have helped me
out in the past and I am very grateful. I w
I began work with the 4.1 version of ActiveMQ, but initially experienced
problems as all messages (at least their ids) had to reside in memory, which
would not work for large data sets. I started work with a Snapshot of the
5.0 release and after 5.0 became production ready, continued with that.
and I am hoping someone here can make that possible. I work in a group that
uses Perl for a large, distributed system. I came upon ActiveMQ while
looking to replace our existing Messaging system. I was awed by the sheer
number of features. But then I realized something.
It just doesn't work.
e remaining active
> consumer on B2. This is probably because 'dynamicOnly' is set to false by
> default. Hope this helped - Joe
>
>
>
>
>
> cmagoyrk wrote:
>>
>> I would like to setup a network of brokers on a set of boxes (b1, b2,
>> bn).
I would like to setup a network of brokers on a set of boxes (b1, b2, bn).
The brokers will allow an arbitrary producer to place a message on a queue,
have a consumer connect to any of the brokers, and consume that message.
That is fairly well documented. What I am concerned with is, if a produ
I can implement that logic into my client, essentially each queue having it's
own error queue, but then what is the purpose of the Dead Letter Queue?
James.Strachan wrote:
>
> On 03/12/2007, cmagoyrk <[EMAIL PROTECTED]> wrote:
>>
>> I am using Client Acknowledgem
I am using Client Acknowledgement with prefetch size set to one. A client
reads a message, decides that the message is invalid, and would like to Nack
it. I do not know how to Nack the message (send a Poison Ack) back to the
Queue. For reference I am trying to do this from a perl application us