activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully" <>
Subject Re: AMQ-5.2.0 RC3: JMS Exception Could not correlate acknowledgment with dispatched message
Date Thu, 13 Nov 2008 09:48:21 GMT
I think the interesting bit is the batch logic in the consumers.
Could you raise a jira and post your test case?
If you could coerce the broker, producers and consumers into a single
java application so that it can be converted into a junit test case it
would be great.

The key to pining this down is the reproducible test case. 1000 m/s
and/or running on a single host should not be a problem.

2008/11/13 bonnyr <>:
> All,
> We've been using AMQ for a while now, and wanted to test the upcoming
> release to see if it resolved
> a problem we're having with the current version we're using (5.1.0), so I've
> setup a test to try
> and create the problem in my test environment.
> My setup is:
> -----------
> 1 producer, producing messages to a queue at a high rate (~1000 m/s). The
> message payload is a
>   simple POJO we use for our project.
> 2 consumers connected to the same queue, one as primary and the other as
> secondary (arbitrary
>   designation, but done such that the primary will be collecting the
> messages if it's connected).
>   each consumer consumes messages in a batch (some glue layer in our app
> does this), and simply
>   acknowledges the last message in the batch.
> 1 broker hosting the queue.
> All 4 executables are running on the same host. All AMQ clients are written
> in  Java. Test is running on WinXP SP3
> After executing for a little while, I am getting the exception in the title.
> Once it occures, the simple
> test clients are simply disconnected and hang, not able to receive any more.
> Can someone suggest a way to try and pin this down? Is this a performance
> problem? Is it related to
> the fact that it's running on the same host?
> Any help will be appreciated.
> Cheers,
> Bonny.
> PS. the production/consumption rate seems to get stuck at around 1000 m/s
> which is quite a bit lower
> than when we originally tested (with 4.1.1) - any idea on what I can do to
> improve this?
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at

View raw message