Tim, in may scenario I want to consume N messages in N consumers, one for each. My consumers wait on a barrier only to show the parallelism, and to show that none of them processed two messages or more. Maybe my Camel configuration is wrong, or there is something wrong with the broker configuration.
On Mon Feb 02 2015 at 6:17:38 PM Tim Bain <tb...@alumni.duke.edu> wrote: > Why do your consumers all wait for the Nth message to be received before > they return to process another? Why don't you use an AtomicInteger to > subtract one each time, and succeed if you hit 0 and fail if you haven't > hit 0 by the end of your timeout interval? Based on what you've shows us > so far, this appears to be an artifact of your test code, not a problem > with the broker. > > On Mon, Feb 2, 2015 at 1:02 PM, Thiago Kronig <thiagokro...@gmail.com> > wrote: > > > Hi list. > > > > I'm trying to concurrently consume 10 messages sent to an embedded > ActiveMQ > > broker over the VM transport. Sometimes my code works, sometimes it hangs > > at the n-th message, randomly. > > > > If I change to a JBossMQ, my Camel client works. > > > > Can someone help me in setting my ActiveMQ broker? > > > > Source at: https://github.com/thiagokronig/activemq-camel-test > > > > Thanks in advance. > > >
