Gary Tully wrote
>
> The message persistence to disk with a sync write,
> with the sender must wait for, is carried out in parallel with the
> message dispatch to a waiting consumer.
>
This is interesting. So it's possible that even before the producer client
has received the response to the
Found the culprit. The issue was in the TestCode
The prefetch limit was not getting set correctly. Setting it through the
props file was not happening.
I tried with explicit setting of this property through the following, and
the concurrency worked as expected
*((ActiveMQConnectionFactory)connect
Hi,
I wrote up a sample message consumer app to test AMQ message processing
functionality.
The app creates a single broker connection and 3 consumer sessions, each
further creating a separate MessageConsumer object. The message consumers
are registered to a queue on the Broker.
Before launching
Thanks Suo!
Actually, I also reached around and found the same answer that the
store-forward makes sure that a message exists in a single broker at a given
point in time.
The source of my original doubt was lack of explanation on how store forward
works in the 'ActiveMQ in action' book, which I
Hi,
As I understand,broker networks could be configured with bidirectional
message push for cross-geographic fail over of message processing through
the store-and-forward method. So, if broker A and B form a simple 2-member
network,possibly over a WAN (spanning multiple geographies), with
bidirect
